-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Always error out if CCS expression shows up when CCS is not supported #139009
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
Changes from all commits
Commits
Show all changes
37 commits
Select commit
Hold shift + click to select a range
1cfd2ca
Always error out if CCS expression shows up when CCS is not supported
smalyshev 0cc995c
Update docs/changelog/139009.yaml
smalyshev 3c38e78
Better fix with context option
smalyshev c1944c2
bug ref
smalyshev 5664342
Reduce ctor explosion
smalyshev ea87ec0
improve comment
smalyshev 266048a
fix tests
smalyshev f1f63dc
Merge branch 'main' into ccs-not-supported-fix
smalyshev e177894
Fix semantic query tests
smalyshev 734f118
more tests
smalyshev 9217de3
fix test
smalyshev 711f73f
disable bwc
smalyshev 9709893
temp fix for SQL
smalyshev 0bbf320
More test fixes
smalyshev a1bfc7a
Fix test
smalyshev a7e0a17
fix test
smalyshev 4ee6cbe
Merge branch 'main' into ccs-not-supported-fix
smalyshev e83781e
Update comments
smalyshev 2977d97
Update docs/changelog/139009.yaml
smalyshev aba5bea
add test
smalyshev d92f41b
Merge branch 'main' into ccs-not-supported-fix
smalyshev 65d858d
Merge branch 'main' into ccs-not-supported-fix
smalyshev ce6a12b
Merge branch 'main' into ccs-not-supported-fix
smalyshev 61edbc6
Merge branch 'main' into ccs-not-supported-fix
smalyshev 7ca0397
Merge branch 'main' into ccs-not-supported-fix
smalyshev 225e8a9
Revert "Update docs/changelog/139009.yaml"
smalyshev 9b7867e
Merge branch 'main' into ccs-not-supported-fix
smalyshev 30dea66
Update docs/changelog/139009.yaml
smalyshev fe336ed
Merge branch 'main' into ccs-not-supported-fix
smalyshev 589d807
Maybe this is not needed
smalyshev b661188
Merge branch 'main' into ccs-not-supported-fix
smalyshev 83d2c82
Update 139009.yaml
smalyshev e8a6a0e
Merge branch 'main' into ccs-not-supported-fix
smalyshev f9965a8
rename method to emphasize it ignores remote expressions
smalyshev 92396d7
fix comments
smalyshev a577e26
ws
smalyshev 2c9bc9b
Merge branch 'main' into ccs-not-supported-fix
smalyshev 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| pr: 139009 | ||
| summary: Always error out if CCS expression shows up when CCS is not supported | ||
| area: CCS | ||
| type: bug | ||
| issues: [ 138987 ] |
37 changes: 37 additions & 0 deletions
37
...-api-spec/src/yamlRestTest/resources/rest-api-spec/test/indices.get_mapping/70_remote.yml
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| --- | ||
| setup: | ||
| - do: | ||
| indices.create: | ||
| index: test_1 | ||
|
|
||
| --- | ||
| "Remote index mapping, should fail": | ||
| - requires: | ||
| cluster_features: [ "search.indices_boost_remote_index_fix" ] | ||
| reason: "indices_boost remote index fix must be present" | ||
| - do: | ||
| catch: /Cross-cluster calls are not supported in this context but remote indices were requested:/ | ||
| indices.get_mapping: | ||
| index: remote1:test_1 | ||
|
|
||
| --- | ||
| "Remote and local index mapping, should fail": | ||
| - requires: | ||
| cluster_features: [ "search.indices_boost_remote_index_fix" ] | ||
| reason: "indices_boost remote index fix must be present" | ||
| - do: | ||
| catch: /Cross-cluster calls are not supported in this context but remote indices were requested:/ | ||
| indices.get_mapping: | ||
| index: test_1,remote1:test_1 | ||
|
|
||
| --- | ||
| "Remote index mapping, ignore_unavailable=true, should fail": | ||
| - requires: | ||
| cluster_features: [ "search.indices_boost_remote_index_fix" ] | ||
| reason: "indices_boost remote index fix must be present" | ||
| - do: | ||
| catch: /Cross-cluster calls are not supported in this context but remote indices were requested:/ | ||
| indices.get_mapping: | ||
| ignore_unavailable: true | ||
| index: remote1:test_1 | ||
|
|
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
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
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
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.
(asking to learn) Why does this need to go into a NodeFeature?
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.
Why did you make it a node feature? I am wondering if an API capability is more appropriate.
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'm not sure how to make it work as API capability - which API would this capability relate to? This happens across multiple APIs... I could link it to a random API, e.g.
_mappingsbut is that more correct?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 we should link it to all the affected APIs, shouldn't we?
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.
All the APIs that use index resolution? Or can use index boosts? That could be a lot of them, and I am not sure how to practically do that. I don't think just having a test justifies changing every API that uses a feature (I am not even sure there's a way to reliably find them?), there should be some better way, unless I miss something?
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 was referring to the APIs that use index resolution but their behaviour changes with this.
Considering that this is only relevant for testing, so I would add it to the APIs you are testing, in this case the mapping, the index boosts and any other you choose to test.
Unless I am mistaken API capabilities were the recommended way to capture API (and behaviour) changes. Do you think that's not the case?