You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2011/08/10 13:10:27 UTC
[jira] [Commented] (LUCENE-3368) IndexWriter commits update
documents without corresponding delete
[ https://issues.apache.org/jira/browse/LUCENE-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082283#comment-13082283 ]
Michael McCandless commented on LUCENE-3368:
--------------------------------------------
Nice catch Simon!
> IndexWriter commits update documents without corresponding delete
> -----------------------------------------------------------------
>
> Key: LUCENE-3368
> URL: https://issues.apache.org/jira/browse/LUCENE-3368
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/index
> Affects Versions: 3.0, 3.0.1, 3.0.2, 3.0.3, 3.1, 3.2, 3.3
> Reporter: Simon Willnauer
> Assignee: Simon Willnauer
> Fix For: 3.4
>
> Attachments: LUCENE-3368.patch
>
>
> while backporting the testcase from LUCENE-3348 I ran into this thread hazard in the 3.x branch. We actually fixed this issue in LUCENE-3348 for Lucene 4.0 but since DWPT has a slightly different behavior when committing segments I create a new issue to track this down in 3.x. when we prepare a commit we sync on IW flush the DW and apply all deletes then release the lock, maybeMerge and start the commit (IW#startCommit(userdata)). Yet, a new segment could be flushed via getReader and sneak into the SegementInfos which are cloned in IW#startCommit instead of in prepareCommit right after the flush.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org