Refactor an ambigious TermVectorsRequest constructor. #35614
Merged
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.
When we deprecate types, we'll want to introduce the constructor
TermVectorsRequest(String index, String id)
. However, this will clash with the current constructorTermVectorsRequest(String index, String type)
, making it difficult to signal the migration path.This PR refactors the constructor to avoid ambiguity. I don't think this change will have much effect on users, since the terms vector HLRC method isn't yet released.