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
NullPointerException in QueryRewriter.java #13
Comments
eeeebbbbrrrr
added a commit
that referenced
this issue
Aug 8, 2015
eeeebbbbrrrr
added a commit
that referenced
this issue
Aug 8, 2015
The underlying problem was that when an ASTNestedGroup was removed, its siblings were no longer accessible due to ordinal renumbering. So the fix is to temporarily store the collection of child nodes before doing any optimization of nested groups.
eeeebbbbrrrr
added a commit
that referenced
this issue
Aug 9, 2015
eeeebbbbrrrr
added a commit
that referenced
this issue
Aug 9, 2015
The underlying problem was that when an ASTNestedGroup was removed, its siblings were no longer accessible due to ordinal renumbering. So the fix is to temporarily store the collection of child nodes before doing any optimization of nested groups.
eeeebbbbrrrr
added a commit
that referenced
this issue
Feb 1, 2017
eeeebbbbrrrr
added a commit
that referenced
this issue
Nov 10, 2020
…armaeter (we default to 'constant_score') and also find_link_for_field() was bugged
eeeebbbbrrrr
added a commit
that referenced
this issue
Jan 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An index option configuration that links multiple indexes:
can cause an NPE in the Elasticsearch plugin when both named indexes are used in a single query, such as:
The full stack is:
The text was updated successfully, but these errors were encountered: