[
https://issues.apache.org/jira/browse/LUCENE-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950785#comment-13950785
]
Rodrigo Vega commented on LUCENE-2679:
--------------------------------------
I actually have "interleaved adds & deletes " and it fails kind of randomly.
There is any work around i can use?
> IndexWriter.deleteDocuments should have option to not apply to docs indexed
> in the current IW session
> -----------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2679
> URL: https://issues.apache.org/jira/browse/LUCENE-2679
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Fix For: 4.8
>
>
> In LUCENE-2655 we are struggling with how to handle buffered deletes,
> with the new per-thread RAM buffers (DWPT).
> But, the only reason why we must maintain a map of del term -> current
> docID (or sequence ID) is to correctly handle the interleaved adds &
> deletes case.
> However, I suspect that for many apps that interleaving never happens.
> Ie, most apps delete only docs from *before* the last commit or NRT
> reopen. For such apps, we don't need a Map... we just need a Set of
> all del terms to apply to past segments but not to the currently
> buffered docs.
> And, importantly, with LUCENE-2655, this would be a single Set, not
> one per DWPT. It should be a a healthy RAM reduction on buffered
> deletes, and should make the deletes call faster (add to one set instead of
> N maps).
> We of course must still support the interleaved case, and I think it
> should be the default, but I think we should provide the option for
> the common-case apps to take advantage of much less RAM usage.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
