Align Discover querying infrastructure #99161
Labels
discuss
Feature:Discover
Discover Application
Icebox
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:needs-research
This issue requires some research before it can be worked on or estimated
Team:DataDiscovery
Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
technical debt
Improvement of the software architecture and operational architecture
Discover currently has a rather fragmented querying infrastructure. We use SearchSource in a couple of places, in others not. We use different querying mechanisms (different implementations to build the query) for different parts of the UI altogether. This has also caused several issues and inconsistencies in the past now. We should take a step back and evaluate that situation and see what improvements we can make to align the querying infrastructure inside Discover as much as possible, and bring the parts that are not yet fully integrated with the
data
services onto them.The text was updated successfully, but these errors were encountered: