DFS modes can cause undefined behaviour in 0.90 #3012
Assignees
Labels
Comments
ghost
assigned
s1monw
added a commit
to s1monw/elasticsearch
that referenced
this issue
May 8, 2013
Lucene provides a set of statistics that depend on the codec / postingsformat as well as on the index options used when the field is created / indexed. If a certain stats value is not available lucene return `-1` instead of the correct value. We need to ensure that those values are encoded correctly if we try to write vLongs as well as when we aggregate those values. Closes elastic#3012
This was referenced May 8, 2013
s1monw
added a commit
that referenced
this issue
May 8, 2013
Lucene provides a set of statistics that depend on the codec / postingsformat as well as on the index options used when the field is created / indexed. If a certain stats value is not available lucene return `-1` instead of the correct value. We need to ensure that those values are encoded correctly if we try to write vLongs as well as when we aggregate those values. Closes #3012
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Lucene provides a set of statistics that depend on the codec / postingsformat as well as on the index options used when the field is created / indexed. If a certain stats value is not available lucene return `-1` instead of the correct value. We need to ensure that those values are encoded correctly if we try to write vLongs as well as when we aggregate those values. Closes elastic#3012
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently some of the transport protocols are broken if Term/FieldStatistics don't provide all optional information. For instance we use
totalTermFrequencyin the TermStats but if you omit the term frequency thetotalTermFrequencyis a negative 1 (-1). This also happens if an index gets upgrade to 0.90 from a 0.20 version that runs lucene 3.6 and doesn't have these stats so they are -1 by default. This seems to be the cause for #3008 as well as #2932 which eventually fail with NPE since the reading behavior of vlongs is undefined.The text was updated successfully, but these errors were encountered: