Combine es and ese search strategies #118165
Labels
discuss
Feature:Search
Querying infrastructure in Kibana
Icebox
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:medium
Medium Level of Effort
Team:DataDiscovery
Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
We currently have an
es
strategy (the old OSS strategy), which can only request data via_search
and theese
search strategy, which supports async search and rollups. I feel this is a bit of a weird (most likely historical grown mix), since e.g. if you're using thees
strategy to not get async search you'd automatically also lose access to querying rollup.I wanted to discuss if it could be worth merging those two into one es search strategy, where async search and rollup support would simply be available parameters to turn it off or on. I feel that way it might be easier to maintain them in the future, especially if we'll start adding support for other features into them.
The text was updated successfully, but these errors were encountered: