-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Split Discover query into three #69134
Labels
blocked
enhancement
New value added to drive a business result
Feature:Discover
Discover Application
performance
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Comments
timroes
added
Feature:Discover
Discover Application
performance
enhancement
New value added to drive a business result
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
labels
Jun 15, 2020
Pinging @elastic/kibana-app (Team:KibanaApp) |
This comment (#76307 (comment)) has a couple of more up-to-date details on the splitting of queries. |
Technical notes After splitting queries (and #55975 which I will close to sum them both up in this issue) the logic of Discover should be as follows:
|
|
4 tasks
7 tasks
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
blocked
enhancement
New value added to drive a business result
Feature:Discover
Discover Application
performance
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
It would be better for performance reasons, if we would split the Discover query which currently loads the data for the chart on top and the document list into two queries (one for the documents, one for the chart on top). That aggregation query can then run potentially slower and doesn't block us from seeing the documents already.
This will also be a requirement for #55975, because if we're doing the aggregation in the same request, we will not have much performance win, from not requesting the total hits.
The text was updated successfully, but these errors were encountered: