-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Search] Remove unnecessary encoding/decoding of the ES-response in Kibana server #189640
Comments
Pinging @elastic/appex-sharedux (Team:SharedUX) |
@dmlemeshko - Looked at this during our Triage today, doesn't seem related to our catalog. Shouldn't this be the disco and viz teams? Or am I missing something bud? |
@petrklapka This is for now in the AnalystXp team. I created this as a compagnon ER for #186139, to track items a little bit more fine grained. cc @lukasolson |
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
#191003 is a PoC of this specifically for ES|QL. |
Remove decoding and re-encoding of the ES-response from Kibana-server. Resolves elastic#189640
Remove decoding and re-encoding of the ES-response from Kibana-server. Resolves elastic#189640 (cherry picked from commit 7b81bcf)
Describe the feature:
Remove decoding and re-encoding of the ES-response from Kibana-server. The elasticsearch-js client now does this by default. Using the
asStream
option will avoid this.Describe a specific use case for the feature:
This is a performance improvement (see outcomes listed here #184713)
For async-search, this is blocked by elastic/elasticsearch#109576.
Tasks
The text was updated successfully, but these errors were encountered: