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
{{ message }}
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
You are right that query should be on a single line and it is user's responsibility to provide it without line breaks to Jest just as they would do to ES. There is no line break replacement on Jest side to counter this because it's bit of a destructive process that could potentially effect the actual data.
As for the fact that query element is present twice: the outer query element inserted by MultiSearch should not have been there, probably result of an assumption carried out from past, I have fixed that now.
I'm not sure exactly if I use multisearch correctly but I've a request produced by Jest like this :
However, this is not correct, it should have been
(Everything on the same line, only one query)
I used a query build to build the Search into the Multisearch object :
List searches = new ArrayList<>();
// build Searches
MultiSearch multiSearch = new MultiSearch.Builder(searches).build();
Any idea what could be wrong ?
The text was updated successfully, but these errors were encountered: