-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[CPS] Search with MRT=true #137701
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
Merged
Merged
[CPS] Search with MRT=true #137701
Changes from 9 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
ec12300
resolve indices when MRT is true
prwhelan d732b40
fan out within search action
prwhelan 5b35c5b
Merge branch 'main' into ES-12853
prwhelan 79b7f66
checkstyle lol
prwhelan 161ca5e
Add unit tests
prwhelan 95fee97
move back to coordinator thread on complete
prwhelan 6255768
Merge branch 'main' into ES-12853
prwhelan bc617da
Revert "Add unit tests"
prwhelan 497e80a
remove local resolution
prwhelan 5e721da
more docs, more tests
prwhelan 6a524c4
Merge branch 'main' into ES-12853
prwhelan ca8dd02
Merge branch 'main' into ES-12853
prwhelan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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 feel like I'm missing something. This statement:
doesn't seem right to me. The check that guarantees this is the call to
CrossProjectIndexResolutionValidator.validateinmergeResolvedIndices, isn't it?Uh oh!
There was an error while loading. Please reload this page.
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 think it's a guarantee on the map's (
remoteIndices) structuring rather than a behaviour ascertaining. Either way, my opinion is that it's not immediately clear what the doc means, unless you're by default familiar with the CPS specifics. Could this be rewritten or clarified?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.
Lines 268 through 280 iterates over a map of ResolvedIndexExpressions and filters the internal list of ResolvedIndexExpression for entities that have
.localIndexResolutionResult() == SUCCESSand at least one index.For example, if
project-1had the original index expressionlogs*map to indices["logs-1", "logs-2"], then the result hasproject-1map to["logs*"]. Ifproject-1hadlogs*map to[], thenproject-1is not included in the resulting map.So, each remote project that is keyed in the resulting
ResolvedIndiceshas at least one index that is mapped from the original index expression.The thing I would like to verify is the assumption that we made in the slack thread, where we set the remote project's index in the OriginalIndices to be the original index expression and not the resolved index (e.g.
["logs*"]and not["logs-1", "logs-2"].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.
That's right. We want to associate with the user input index expressions and not the resolved values. You're on the right track.