lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] [Created] (LUCENE-3368) IndexWriter commits update documents without corresponding delete
Date Tue, 09 Aug 2011 12:39:27 GMT
IndexWriter commits update documents without corresponding delete

                 Key: LUCENE-3368
             Project: Lucene - Java
          Issue Type: Bug
          Components: core/index
    Affects Versions: 3.3, 3.2, 3.1, 3.0.3, 3.0.2, 3.0.1, 3.0
            Reporter: Simon Willnauer
             Fix For: 3.4

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:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message