Enhance refresh policy handling #2725
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Besides defining the global value for the refresh policy in the client configuration it was already possible to change the refresh policy by calling
setRefreshPolicy(RefreshPolicy)on the provided implementations of theElasticsearchOperationsandReactiveElasticsearchOperationsinterfaces.For easier handling when using these interfaces they both now offer a
withRefreshPolicy(RefreshPolicy)method which will return a copy of the operations instance that uses the same client, converter, mapper etc, but has a different refresh policy set.For users of the repository interfaces
ElasticsearchRepositoryandReactiveElasticsearchRepositorythere are new overloads of the methods that might need a refresh policy (save and delete) having an additional parameter of theRefreshPolicytype.Closes #2722