-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Wildcard cluster names for cross cluster search #23893
Copy link
Copy link
Closed
Labels
:Data Management/Indices APIsDO NOT USE. Use ":Distributed/Indices APIs" or ":StorageEngine/Templates" instead.DO NOT USE. Use ":Distributed/Indices APIs" or ":StorageEngine/Templates" instead.:Search/SearchSearch-related issues that do not fall into other categoriesSearch-related issues that do not fall into other categories>enhancement
Description
With cross cluster search today, each cluster has to be specified separately, eg
GET one:*,two:*,three:*/_search
It would be good to be able to support wildcards:
GET *:*/_search
By extension, (because it is how it works everywhere else), we should support pattern matching like:
GET t*:*/_search
One complication is that : is an allowed character in index names today (although we have plans to deprecate #23892). We can work around this with the following logic:
- if remote clusters are not configured, treat the specified name as an index name
- if remote clusters ARE configured, treat everything before the first
:as a cluster name
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Data Management/Indices APIsDO NOT USE. Use ":Distributed/Indices APIs" or ":StorageEngine/Templates" instead.DO NOT USE. Use ":Distributed/Indices APIs" or ":StorageEngine/Templates" instead.:Search/SearchSearch-related issues that do not fall into other categoriesSearch-related issues that do not fall into other categories>enhancement
Type
Fields
Give feedbackNo fields configured for issues without a type.