BitVector.isSparse is sometimes wrong
-------------------------------------
Key: LUCENE-3254
URL: https://issues.apache.org/jira/browse/LUCENE-3254
Project: Lucene - Java
Issue Type: Bug
Components: core/other
Reporter: Michael McCandless
Assignee: Michael McCandless
Fix For: 3.4, 4.0
In working on LUCENE-3246, I found a few problems with
BitVector.isSparse:
* Its math can overflow int, such that if there are enough deleted
docs and maxDoc() is largish, isSparse may incorrectly return true
* It over-estimates the size of the sparse file, since when
estimating number of bytes for the vInt dgaps it uses bits.length
instead of bits.length divided by number of set bits (ie, the
"average" gap between set bits)
This is relatively harmless (just affects performance / size of .del
file on disk, not correctness).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
