-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Return the same point in time in search response #64188
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
Conversation
|
Pinging @elastic/es-search (:Search/Search) |
jimczi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
server/src/main/java/org/elasticsearch/action/search/AbstractSearchAsyncAction.java
Show resolved
Hide resolved
|
run elasticsearch-ci/packaging-sample-unix |
With this change, we will always return the same point in time in a search response as its input until we implement the retry mechanism for the point in times.
With this change, we will always return the same point in time in a search response as its input until we implement the retry mechanism for the point in times.
| boolean includeSearchContextInResponse() { | ||
| return request.pointInTimeBuilder() != null; | ||
| boolean buildPointInTimeFromSearchResults() { | ||
| // TODO: Until we implement the retry mechanism for point in times (i.e., replace an unavailable shard with an equivalent copy), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed this TODO while working on an unrelated refactor. Do we need to address the TODO now that we retry point-in-times (#66713)?
With this change, we will always return the same point in time in a search response as its input until we implement the retry mechanism for the point in times.