Missing required property 'InferenceChunkingSettings.service'

[swallez]

After upgrading a cluster to version 8.17.3 Java API client version 8.16 produces an error for with the following request:

final List<InferenceEndpointInfo> endpoints = esClient().inference().get(new GetInferenceRequest.Builder().inferenceId("_all").build()).endpoints();

co.elastic.clients.transport.TransportException: node: *****, status: 200, [es/inference.get] Failed to decode response
    at co.elastic.clients.transport.ElasticsearchTransportBase.decodeTransportResponse(ElasticsearchTransportBase.java:409)
    at co.elastic.clients.transport.ElasticsearchTransportBase.getApiResponse(ElasticsearchTransportBase.java:367)
    at co.elastic.clients.transport.ElasticsearchTransportBase.performRequest(ElasticsearchTransportBase.java:148)
    at co.elastic.clients.elasticsearch.inference.ElasticsearchInferenceClient.get(ElasticsearchInferenceClient.java:116)
Caused by: co.elastic.clients.json.JsonpMappingException: Error deserializing co.elastic.clients.elasticsearch.inference.InferenceEndpointInfo: co.elastic.clients.util.MissingRequiredPropertyException: Missing required property 'InferenceChunkingSettings.service' (JSON path: endpoints[0].chunking_settings) (line no=1, column no=364, offset=-1)
    at co.elastic.clients.json.JsonpMappingException.from0(JsonpMappingException.java:134)
    at co.elastic.clients.json.JsonpMappingException.from(JsonpMappingException.java:121)
    at co.elastic.clients.json.ObjectDeserializer.deserializeInner(ObjectDeserializer.java:236)
    at co.elastic.clients.json.ObjectDeserializer.deserialize(ObjectDeserializer.java:166)
    at co.elastic.clients.json.ObjectDeserializer.deserialize(ObjectDeserializer.java:157)
    at co.elastic.clients.json.ObjectBuilderDeserializer.deserialize(ObjectBuilderDeserializer.java:85)
    at co.elastic.clients.json.DelegatingDeserializer$SameType.deserialize(DelegatingDeserializer.java:48)
    at co.elastic.clients.json.JsonpDeserializerBase$ArrayDeserializer.deserialize(JsonpDeserializerBase.java:318)
    at co.elastic.clients.json.JsonpDeserializerBase$ArrayDeserializer.deserialize(JsonpDeserializerBase.java:280)
    at co.elastic.clients.json.JsonpDeserializer.deserialize(JsonpDeserializer.java:77)
    at co.elastic.clients.json.ObjectDeserializer$FieldObjectDeserializer.deserialize(ObjectDeserializer.java:78)
    at co.elastic.clients.json.ObjectDeserializer.deserializeInner(ObjectDeserializer.java:214)
    at co.elastic.clients.json.ObjectDeserializer.deserialize(ObjectDeserializer.java:166)
    at co.elastic.clients.json.ObjectDeserializer.deserialize(ObjectDeserializer.java:157)
    at co.elastic.clients.json.JsonpDeserializer.deserialize(JsonpDeserializer.java:77)
    at co.elastic.clients.json.ObjectBuilderDeserializer.deserialize(ObjectBuilderDeserializer.java:79)
    at co.elastic.clients.json.DelegatingDeserializer$SameType.deserialize(DelegatingDeserializer.java:43)
    at co.elastic.clients.transport.ElasticsearchTransportBase.decodeTransportResponse(ElasticsearchTransportBase.java:404)
    ... 61 more
Caused by: co.elastic.clients.util.MissingRequiredPropertyException: Missing required property 'InferenceChunkingSettings.service'
    at co.elastic.clients.util.ApiTypeHelper.requireNonNull(ApiTypeHelper.java:76)
    at co.elastic.clients.elasticsearch.inference.InferenceEndpoint.<init>(InferenceEndpoint.java:80)
    at co.elastic.clients.elasticsearch.inference.InferenceChunkingSettings.<init>(InferenceChunkingSettings.java:76)
    at co.elastic.clients.elasticsearch.inference.InferenceChunkingSettings.<init>(InferenceChunkingSettings.java:60)
    at co.elastic.clients.elasticsearch.inference.InferenceChunkingSettings$Builder.build(InferenceChunkingSettings.java:246)
    at co.elastic.clients.elasticsearch.inference.InferenceChunkingSettings$Builder.build(InferenceChunkingSettings.java:169)
    at co.elastic.clients.json.ObjectBuilderDeserializer.deserialize(ObjectBuilderDeserializer.java:80)
    at co.elastic.clients.json.DelegatingDeserializer$SameType.deserialize(DelegatingDeserializer.java:43)
    at co.elastic.clients.json.ObjectDeserializer$FieldObjectDeserializer.deserialize(ObjectDeserializer.java:78)
    at co.elastic.clients.json.ObjectDeserializer.deserializeInner(ObjectDeserializer.java:214)

[l-trotta]

fixed in elastic/elasticsearch-specification#4095

[mariuszpala]

We get the same error when using 8.17.4 SDK connecting to 8.17 cluster.

co.elastic.clients.transport.TransportException: node: https://develop....es.us-east-1.aws.found.io:443/, status: 200, [es/inference.get] Failed to decode response
at co.elastic.clients.transport.ElasticsearchTransportBase.decodeTransportResponse(ElasticsearchTransportBase.java:409)
at co.elastic.clients.transport.ElasticsearchTransportBase.getApiResponse(ElasticsearchTransportBase.java:367)
at co.elastic.clients.transport.ElasticsearchTransportBase.performRequest(ElasticsearchTransportBase.java:148)
at co.elastic.clients.elasticsearch.inference.ElasticsearchInferenceClient.get(ElasticsearchInferenceClient.java:116)

[l-trotta]

@mariuszpala since the type was completely missing from the specification this will affect all versions of the client, consequently it will be fixed in all versions.

[mariuszpala]

Thank you, where can we expect a fix in 8.17 as it blocks us?

[l-trotta]

8.17.5 should be released next week

[l-trotta]

hey @mariuszpala we just released version 8.16.7 which has the same fix, you could try that one while waiting for 8.17.5

[mariuszpala]

Thank you.

[mariuszpala]

I can see the version in Maven, but our team is not able to use it for some reason:

https://repo1.maven.org/maven2/co/elastic/clients/elasticsearch-java/8.16.7/elasticsearch-java-8.16.7.pom

Maven reports:

Could not resolve dependencies for project XYZ
[ERROR] dependency: org.elasticsearch.client:elasticsearch-rest-client:jar:8.16.7 (compile)
[ERROR] 	Could not find artifact org.elasticsearch.client:elasticsearch-rest-client:jar:8.16.7 in central (https://repo.maven.apache.org/maven2)

The download URL is a bit different also:

Downloading from MavenCentral: https://repo1.maven.org/maven2/org/elasticsearch/client/elasticsearch-rest-client/8.16.7/elasticsearch-rest-client-8.16.7.jar

8.16.6 works just fine. Any idea what is wrong?

		<dependency>
			<groupId>co.elastic.clients</groupId>
			<artifactId>elasticsearch-java</artifactId>
			<version>8.16.7</version>
		</dependency>

[l-trotta]

elasticsearch-rest-client is wrong, that's the id for the low level rest client, which is another artifact. The pom dependency looks fine, I've just tested it with gradle and I can import it normally with:
implementation("co.elastic.clients:elasticsearch-java:8.16.7")
Can you make sure the dependency is written correctly? It shouldn't be elasticsearch-rest-client.
Nevermind it's the transitive dependency, looking into it.

[swallez]

@mariuszpala let me give some explanation on the dependency issue you encountered. It's related to a recent change in the release cycle of the java client.

Previously patch releases were synchronized with Elastic-wide patch releases, which meant that sometimes users had to wait for several weeks for a small bugfix. We now release patch releases of the Java client on an ad-hoc basis, which allows us to be be much more reactive. Version 8.16.7 is the first patch release that is released on an ad-hoc basis.

The problem comes from the fact that our release process uses the exact same version for the Java client and its rest-client dependency. This worked fine with Elastic-wide patch releases, but obviously no more with independent patch releases.

So for this specific version, you should force the version of the rest-client to 8.16.6: org.elasticsearch.client:elasticsearch-rest-client:jar:8.16.6

We're fixing our release process so that it doesn't happen again.

[mariuszpala]

Hi, this just became a huge production issue. So far we got that error when connecting to cluster version 8.17+, but now customer reported that even on 8.16 they get the same version. Are you planning to fix the Maven release or the workaround you mentioned is the only solution?

[swallez]

Sorry, I'm not sure I understand: can you explain what the production issue is? Hasn't this issue surfaced when testing the application after updating dependencies?