[ https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661814#action_12661814 ]

Jason Rutherglen commented on LUCENE-1476:

I like this idea of tombstones and we should figure out a way to support it. This issue https://issues.apache.org/jira/browse/LUCENE-584 had an implementation of a "matcher" class that the scorers implemented which I do not think made it into the committed patch.
I think the inefficiency of needing individual iterator objects applies to OpenBitSet as well, right?
Yes that is true.

For realtime search where a new transaction may only have a handful of deletes the tombstones may not be optimal because too many tombstones would accumulate (I believe). For this scenario rolling bitsets may be better. Meaning pool bit sets and throw away unused readers.
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

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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 91 | next ›
Discussion Overview
groupjava-dev @
postedJan 8, '09 at 12:01a
activeJan 30, '09 at 10:47p



site design / logo © 2021 Grokbase