You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jason Rutherglen (JIRA)" <ji...@apache.org> on 2011/01/24 22:18:16 UTC
[jira] Closed: (LUCENE-1533) Deleted documents as a Filter or top
level Query
[ https://issues.apache.org/jira/browse/LUCENE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Rutherglen closed LUCENE-1533.
------------------------------------
Resolution: Won't Fix
Won't be working on these and they're old
> Deleted documents as a Filter or top level Query
> ------------------------------------------------
>
> Key: LUCENE-1533
> URL: https://issues.apache.org/jira/browse/LUCENE-1533
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.4
> Reporter: Jason Rutherglen
> Priority: Minor
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> In exploring alternative and perhaps faster ways to implement the
> deleted documents functionality, the idea of filtering the deleted
> documents at a higher level came up. This system would save on
> checking the deleted docs BitVector of each doc read from the posting
> list by SegmentTermDocs. This is equivalent to an AND NOT deleted
> docs query.
> If the patch improves the speed of indexes with delete documents,
> many core unit tests will need to change, or alternatively the
> functionality provided by this patch can be an IndexReader option.
> I'm thinking the first implementation will be a Filter in
> IndexSearcher.
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org