Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MissingRequiredPropertyException in PIT query #921

Open
floorleap opened this issue Dec 17, 2024 · 1 comment
Open

MissingRequiredPropertyException in PIT query #921

floorleap opened this issue Dec 17, 2024 · 1 comment

Comments

@floorleap
Copy link

Java API client version

8.17.0

Java version

17 (kotlin 2.0.x)

Elasticsearch Version

8.17.0

Problem description

Hi, I'm getting an exception when running a PIT request. The missing field is OpenPointInTimeResponse.shards. . Filing a bug as requested in the docs.

I initially posted in a different ticket. I was told there it is probably related to this recent change. The elasticsearch server should always send _shard in the response from version 8.16.0 forward.

Thanks!


The first error was caused by: node: https://localhost:50388/, status: 200, [es/open_point_in_time] Failed to decode response
co.elastic.clients.transport.TransportException: node: https://localhost:50388/, status: 200, [es/open_point_in_time] 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.ElasticsearchClient.openPointInTime(ElasticsearchClient.java:1809)
[...]

Caused by: co.elastic.clients.util.MissingRequiredPropertyException: Missing required property 'OpenPointInTimeResponse.shards'

cc @l-trotta

@l-trotta
Copy link
Contributor

Hey!
Could you let me know how you are performing the OpenPointInTimeRequest? I just tried to reproduce the issue with a 8.17.0 server instance and it looks like the shards field is indeed always returned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants