[
https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662345#action_12662345
]
Michael McCandless commented on LUCENE-1476:
--------------------------------------------
{quote}
> We could potentially make that choice with Lucy/KS, thus allowing us to remove
> the deletions check in the PostingList iterator (as above) and getting a
> potential speedup. But even then I hesitate to push the deletions API upwards
> into a space where users of raw Scorer and TermDocs classes have to deal with
> it - especially since iterator-style deletions aren't very user-friendly.
{quote}
Can't you just put sugar on top? Ie, add an API that matches today's
API and efficiently applies the "deleted docs filter" for you? Then
you have 100% back compat?
> 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: [email protected]
For additional commands, e-mail: [email protected]
