-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
Internal server error when searching using _source
and object field set to an array mixing non-empty and empty objects
#92814
Comments
Pinging @elastic/es-search (Team:Search) |
Looks like a duplicate of #92480, closing this. |
@DaveCTurner Are you sure about that? While the symptoms are similar, my bug occurs only in 8.6.0, and not in 8.5.3, while #92480 was reported against 8.5.3... |
It looks like a duplicate in the sense that it appears to be hitting the same Jackson bug, and that upgrading Jackson (see #92763) fixes it. |
this will be fixed by #92984 |
That's great to hear, thanks a lot! |
Elasticsearch Version
8.6.0
Installed Plugins
none
Java Version
bundled
OS Version
Linux yrodiere.redhat 6.0.15-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Dec 21 18:33:23 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Problem Description
On Elasticsearch 8.6.0, the
_source
feature in the_search
endpoint seems unable to parse documents where an object field is set to an array mixing non-empty and empty objects (e.g.{"myobject":[{"mykeyword": "foo"}, {}]}
; it fails with an internal server error.This used to work without error in Elasticsearch 8.5.3.
Interestingly, an array containing only empty objects (e.g.
{"myobject":[{"mykeyword": "foo"}, {}]}
) works fine; you really need to mix empty and non-empty objects to trigger the failure.Here is the error returned by Elasticsearch 8.6.0:
Steps to Reproduce
Logs (if relevant)
Output of the script above on Elasticsearch 8.6.0:
Output of the script above on Elasticsearch 8.5.3:
The text was updated successfully, but these errors were encountered: