[
https://issues.apache.org/jira/browse/LUCENE-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920606#action_12920606
]
Jason Rutherglen commented on LUCENE-2655:
------------------------------------------
If there are 2 DWPTs, and each has a the following pending deletes:
DWPT #1 maxdoc: 50; term id:1 limit:25
DWPT #2 maxdoc: 45; term id:1 limit:30
Where limit is the docid-upto stored as an int value in the pending deletes
map. If we flush one of these DWPTs without first applying the deletes to a
bitvector, and we flush the DWPTs in order, then DWPT #1 would flush the
deletes, the term doc limit would be reset to segmentinfos maxdoc + 25.
However there' a 50 - 25 = 25 gap. When DWPT #2 is flushed, the limit for term
id:1 is set to segmentinfos maxdoc + 50 + 30. eg, we're effectively losing
DWPT #1s limit (26 - 50)?
> 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
