-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Add Chunked rest encoding for Search APIs #95661
Comments
Pinging @elastic/es-search (Team:Search) |
Hey, can i pick this up? |
Hi @AkisPanagiotopoulos, thanks for your interest! This is a fairly involved project so probably not the best to pick up for an external contributor yet. Once #94736 has been added the AsyncSearchResponse and SearchTemplateResponse changes will be fairly small and self-contained so it might be worth revisiting then? If you're looking for something to start off with, searching on the |
As a prerequisite to making search responses use chunked REST serialization, we need to ensure that no exceptions are thrown when toXContent gets called. DocumentFields can currently throw exceptions if their contained values are not serializable. This commit changes the serialization code here to replace unserializable values with a placeholder value rather than failing the whole request. Relates to #95661
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
Description
This issue is to track adding chunked rest encoding to our various search APIs. Linked to #89838
We will also investigate adding further chunking to SearchResponse, which currently does not break up aggregations.
The text was updated successfully, but these errors were encountered: