-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Point In Time - does not support having a body #8396
Comments
If someone else do have the issue you can replace the code with the following request using the Transport instead. Until a working solution is in place.
|
Hi @HaggeMan, thanks for providing a workaround. Recent versions of Elasticsearch (I tested with 8.15.2) do accept a body with an There is no way for the client to tell, if you used that property in the body or not. This causes a body to be sent in all cases. ES 8.15.2 accepts an empty body without returning that validation error, but previous versions (at least the 8.13.2 you are currently using) does not allow a body. I'm not sure why the Elasticsearch server introduced such a breaking change in a minor version, but I sadly can't do anything to fix this on client side. The client is stateless and does not know to which version of the server it speaks. |
@flobernd thanks for the update. We'll update to latest elastic version shortly and can then start using the method. I'll close the issue. |
Elastic.Clients.Elasticsearch version: 8.13.2
Elasticsearch version: 8.13.2
.NET runtime version: 8.15.10
Operating system version: Windows 11
Description of the problem including expected versus actual behavior:
Steps to reproduce:
Expected behavior
The client should not send {} in the body
Provide
DebugInformation
(if relevant):This is how it looks like when sending the body like the client...
When sending an empty body...
The text was updated successfully, but these errors were encountered: