[
https://issues.apache.org/jira/browse/LUCENE-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727623#action_12727623
]
Tim Smith commented on LUCENE-1721:
-----------------------------------
bq. Sounds like you could perhaps use reopen() or the NRT (near realtime)
patches - get a new reader, see what segments changed (if any).
Yeah, i'm aware of all these (and will take advantage of them once 2.9 is out),
but some custom caches may not work on a per segment basis (may be much slower
when evaluated this way, or may not be able to be constructed in the first
place without full index as a context)
was just throwing out that use case, as it is one i have run into and is one
closely related to wanting to delete documents by internal id.
> IndexWriter to allow deletion by doc ids
> ----------------------------------------
>
> Key: LUCENE-1721
> URL: https://issues.apache.org/jira/browse/LUCENE-1721
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Shay Banon
>
> It would be great if IndexWriter would allow for deletion by doc ids as well.
> It makes sense for cases where a "query" has been executed beforehand, and
> later, that query needs to be applied in order to delete the matched
> documents.
> More information here:
> http://www.nabble.com/Delete-by-docId-in-IndexWriter-td24239930.html
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
