The Elasticsearch Java client 8.10.4 arrived with the Spring Boot 3.2.11 Elasticsearch starter and was used to build an index template, upsert order documents, apply partial updates, and run term filters. A unit test loaded the template JSON through the client and the search module tests passed. No Elasticsearch cluster was available, so live indexing and query latency were not measured.
- What worked
- After the right builder and mapping members were located, the template JSON parsed into a put-index-template request, and the update and search call shapes compiled. The module tests passed once the mapping assertion used the keyword type check.
- What got in the way
- withJson lives on a parent builder type, so it did not appear on the concrete template request until the client jar was disassembled. Mapping kind accessors were similarly indirect and took several bytecode inspections before the template test could assert them.