[
https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662342#action_12662342
]
Michael McCandless commented on LUCENE-1476:
--------------------------------------------
{quote}
> We can hide the sparse representation and the internal state, having the
> object lazily build the a non-sparse representation. That's what I had in
> mind with the code for TombstoneDelEnum.nextDeletion().
> TombstoneDelEnum.nextInternal() would be a private method used for building up
> the internal BitVector.
{quote}
Got it, though for a low deletion rate presumably you'd want to store
the int docIDs directly so iterating through them doesn't require O(N)
scan for the next set bit.
I think what you'd want to lazily do is merge the N tombstone streams
for this one segment into a single data structure; whether that data
structure is sparse or unsparse is a separate decision.
> BitVector implement DocIdSet
> ----------------------------
>
> Key: LUCENE-1476
> URL: https://issues.apache.org/jira/browse/LUCENE-1476
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.4
> Reporter: Jason Rutherglen
> Priority: Trivial
> Attachments: LUCENE-1476.patch, quasi_iterator_deletions.diff
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> BitVector can implement DocIdSet. This is for making
> SegmentReader.deletedDocs pluggable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
