SQL: Add ability to perform CCS through SQL querying (backport of #78903) #79536
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
This adds the ability to perform cross cluster searching through SQL. This is done by simply using the CCS-specific `cluster:index` notation, where the "cluster" maps to an SQL catalog and "index" to a table; patterns are supported for both. Noteworthy here is that a search runs either on the local or remote clusters, but not both (which is a CCS-specific behaviour). Another limitation is currently that table enumeration in remote clusters will not contain aliases (not reported through field caps). Also, frozen indices are currently not listed as such (they're listed as normal indices). `SYS COLUMNS` command will not take a catalog pattern - an exact match is required -, following xDBC spec. `SYS TABLES` can, however. This adds a new "catalog" request parameter, to be used by the xDBC clients. It's value is whatever the set-catalog xDBC action is passed to by the application and will have ES/SQL run the query on the indicated cluster, in case the query itself doesn't specify a cluster target (which takes precedence over the parameter). (cherry picked from commit 733837d)
bpintea
added
backport
auto-merge-without-approval
Contributor
|
@elasticmachine run elasticsearch-ci/part-2 |
Remove 'xpack.security.autoconfiguration.enabled' setting.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 adds the ability to perform cross cluster searching through SQL.
This is done by simply using the CCS-specific
cluster:indexnotation,where the "cluster" maps to an SQL catalog and "index" to a table;
patterns are supported for both. Noteworthy here is that a search runs
either on the local or remote clusters, but not both (which is a
CCS-specific behaviour).
Another limitation is currently that table enumeration in remote
clusters will not contain aliases (not reported through field caps).
Also, frozen indices are currently not listed as such (they're listed as
normal indices).
SYS COLUMNScommand will not take a catalog pattern - an exact match isrequired -, following xDBC spec.
SYS TABLEScan, however.This adds a new "catalog" request parameter, to be used by the xDBC
clients. It's value is whatever the set-catalog xDBC action is passed to
by the application and will have ES/SQL run the query on the indicated
cluster, in case the query itself doesn't specify a cluster target
(which takes precedence over the parameter).
(cherry picked from commit 733837d)