You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, thank you for reporting this! I tested it in the newer version of the client and it looks like it's still an issue, which is weird because the json serialization of the request matches exactly what the server should accept. I'll look into this and will update soon!
Found out what's happening: the server does not accept both q as a value when a body is provided, and for simplicity the java client always sends a body for POST requests, even when it's empty. Still undecided on how to fix this, in the meantime the suggested workaround it to perform the same query in the body, like this:
Found out what's happening: the server does not accept both q as a value when a body is provided, and for simplicity the java client always sends a body for POST requests, even when it's empty. Still undecided on how to fix this, in the meantime the suggested workaround it to perform the same query in the body, like this:
Java API client version
8.8.2
Java version
OpenJDK Runtime Environment (Temurin)(build 1.8.0_422-b05)
Elasticsearch Version
8.8.2
Problem description
The text was updated successfully, but these errors were encountered: