Do not use annotations to cache Elasticsearch API calls #2883
Conversation
This file contains 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
I got confused by the comment attached to the `IsMigratingData` function, along with its unit tests. They somehow indicate we're checking if a node has the only copy of a shard. But the reality is we just check if there's any shard on that node. This commit renames the function to `ShardsOnNode()`, modifies the comment accordingly, and adapt the unit tests to the very simple logic of the function.
This commit does not address the remote clusters API call which will be fixed in a following up PR.
sebgl
approved these changes
Apr 15, 2020
anyasabo
approved these changes
Apr 15, 2020
This was referenced Apr 21, 2020
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.
This PR is a backport of #2880 in 1.1.0
It also takes the opportunity to backport the naming improvement from #2845