[
https://issues.apache.org/jira/browse/LUCENE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2897:
---------------------------------------
Fix Version/s: (was: 3.2)
3.1
I think we can do this for 3.1.
> apply delete-by-Term and docID immediately to newly flushed segments
> --------------------------------------------------------------------
>
> Key: LUCENE-2897
> URL: https://issues.apache.org/jira/browse/LUCENE-2897
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-2897.patch, LUCENE-2897.patch
>
>
> Spinoff from LUCENE-2324.
> When we flush deletes today, we keep them as buffered Term/Query/docIDs that
> need to be deleted. But, for a newly flushed segment (ie fresh out of the
> DWPT), this is silly, because during flush we visit all terms and we know
> their docIDs. So it's more efficient to apply the deletes (for this one
> segment) at that time.
> We still must buffer deletes for all prior segments, but these deletes don't
> need to map to a docIDUpto anymore; ie we just need a Set.
> This issue should wait until LUCENE-1076 is in since that issue cuts over
> buffered deletes to a transactional stream.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
