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
I am not sure if this might be an Elastic version or some other issue. We are currently using ELS 7.0, but I setup a blank ELS 8.0 too, which resultet in the same issue.
which at least both available ELS instances (7.0 and 8.0) don't seem to like...
{"error":{"root_cause":[{"type":"parsing_exception","reason":"[query_string] malformed query, expected [END_OBJECT] but found [FIELD_NAME]","line":1,"col":53}],"type":"parsing_exception","reason":"[query_string] malformed query, expected [END_OBJECT] but found [FIELD_NAME]","line":1,"col":53},"status":400}
As far as I can see, all three variants work when changing the code in ElasticsearchSearcher:
Thx for the report. So the issue is to use a EqualCondition and a SearchCondition together. Can you try to provide a failing test case before we have a deeper look how to integrate a fix here, so we first know which search engines fail in this case.
I am not sure if this might be an Elastic version or some other issue. We are currently using ELS 7.0, but I setup a blank ELS 8.0 too, which resultet in the same issue.
The following code works perfect:
Resulting JSON body:
Changing the search configuration to the following code also works:
Resulting JSON body:
However, combining both:
results in the following JSON body:
which at least both available ELS instances (7.0 and 8.0) don't seem to like...
As far as I can see, all three variants work when changing the code in
ElasticsearchSearcher
:The text was updated successfully, but these errors were encountered: