[
https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663837#action_12663837
]
Yonik Seeley commented on LUCENE-1476:
--------------------------------------
bq. IndexReader.getDeletedDocs that returns a DocIdSet
Seems like a good idea, but the difficulty lies in defining the semantics of
such a call.
Are subsequent deletes reflected in the returned DocIdSet? Perhaps make this
undefined - may or may not be.
Can the DocIdSet be used concurrently with IndexReader.deleteDocument()? This
could work (w/o extra undesirable synchronization) if we're careful.
> 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]
