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
AssertionError during percolation using constant score query #5049
Labels
Comments
imotov
added a commit
to imotov/elasticsearch
that referenced
this issue
Feb 7, 2014
Test for elastic#5049, the test doesn't fail but it generates AssertError in the log while running
s1monw
added a commit
that referenced
this issue
Feb 10, 2014
AndDocIdSet#IteratorBasedIterator was potentially initialized with NO_MORE_DOCS which violates the initial state of DocIdSetIterator and could lead to undefined behavior when used in a search context. Closes #5049
s1monw
added a commit
that referenced
this issue
Feb 10, 2014
AndDocIdSet#IteratorBasedIterator was potentially initialized with NO_MORE_DOCS which violates the initial state of DocIdSetIterator and could lead to undefined behavior when used in a search context. Closes #5049
s1monw
added a commit
that referenced
this issue
Feb 10, 2014
AndDocIdSet#IteratorBasedIterator was potentially initialized with NO_MORE_DOCS which violates the initial state of DocIdSetIterator and could lead to undefined behavior when used in a search context. Closes #5049
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
AndDocIdSet#IteratorBasedIterator was potentially initialized with NO_MORE_DOCS which violates the initial state of DocIdSetIterator and could lead to undefined behavior when used in a search context. Closes elastic#5049
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
AndDocIdSet#IteratorBasedIterator was potentially initialized with NO_MORE_DOCS which violates the initial state of DocIdSetIterator and could lead to undefined behavior when used in a search context. Closes elastic#5049
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When elasticsearch is running with assertions enabled, a constant score query that doesn't match a record can cause AssertionError to be thrown. To reproduce start elasticsearch with assertions enabled and execute the following script
on 0.90 branch:
to reproduce on master:
On the master the issue is not as prominent since the error is not returned to the user. On the current master the result of execution of the script above is the following error in the log:
The text was updated successfully, but these errors were encountered: