-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Remove commit information from refresh result #94259
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
base: main
Are you sure you want to change the base?
Conversation
We recently made a change where the refresh result includes information about the current commit. However, this result is tightly tied to the concept of a flush. The refresh method in internal engine does not perform commits or flushes, so this result can be misleading to consumers. This commit extracts a separate method that will perform both a flush and a refresh and then returns the approriate generation.
Pinging @elastic/es-distributed (Team:Distributed) |
I ended up adjusting this just to read the commit stats after performing the refresh (and flush for index engine). I still feel like this is worth considering as I continue to prefer not tie the flush generation to the refresh result since they are not really related. Although if there are objections, we can discuss. |
Pinging @elastic/es-distributed-obsolete (Team:Distributed (Obsolete)) |
Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing) |
We recently made a change where the refresh result includes information about the current commit. However, this result is tightly tied to the concept of a flush. The refresh method in internal engine does not perform commits or flushes, so this result can be misleading to consumers. This commit just reads the flush generation from the commit stats.