[
https://issues.apache.org/jira/browse/LUCENE-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920276#action_12920276
]
Michael McCandless commented on LUCENE-2655:
--------------------------------------------
bq. When a new segment is flushed, then the docid-upto is reset to what's in
the latest segment?
Do you mean the flushedDocCount (in DocumentsWriter), by "docid-upto"? Ie,
this is what we use to "globalize" the docid-upto stored for each delete
Term/Query.
bq. Aren't we then losing point-in-timeness of the docid-uptos per DWPT by
simply resetting dut to the highest value of the newest segment?
I'm confused... that flushedDocCount is just an int, tracking the total doc
count of all already-flushed segments. This shouldn't affect
point-in-timeness....?
> Get deletes working in the realtime branch
> ------------------------------------------
>
> Key: LUCENE-2655
> URL: https://issues.apache.org/jira/browse/LUCENE-2655
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: Realtime Branch
> Reporter: Jason Rutherglen
> Fix For: Realtime Branch
>
> Attachments: LUCENE-2655.patch
>
>
> Deletes don't work anymore, a patch here will fix this.
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
