[BUG] SearchRequest is not serializing the Scroll time parameter #676
Labels
enhancement
New feature or request
Comments
|
@frivard-coveo Still want to try to fix this? I renamed this into a feature request to serialize the additional types. |
dblock
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug?
The Scroll API is not working properly because the ScrollId returned in the SearchResponse has an ill-defined validity.
The root cause appears to be that the SearchRequest
Scrollparameter (or typeTime) is not serialized, and thus the search validity cannot be specified.How can one reproduce the bug?
Create a SearchRequest, and specify a
Scrollwith value"5m", which is 5 minutes.With the search response, use the scroll id to do a ScrollRequest;
most of the time the server replies with "all shards failed".
What is the expected behavior?
The search should success with 0 or more results.
What is your host/environment?
Observed on Alpine Linux (hosted on AWS) and Windows 11 (developer laptop).
Do you have any screenshots?
No, but I have application logs (from our in-house application)
Do you have any additional context?
no.
The text was updated successfully, but these errors were encountered: