[
https://issues.apache.org/jira/browse/LUCENE-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652282#comment-13652282
]
Robert Muir commented on LUCENE-4986:
-------------------------------------
Can we remove synchronized from noDups?
release() is already synced, and it scares me to have additional
synchronization in a method called only by assert: it could hide bugs.
> NRT reader doesn't see changes after successful IW.tryDeleteDocument
> --------------------------------------------------------------------
>
> Key: LUCENE-4986
> URL: https://issues.apache.org/jira/browse/LUCENE-4986
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 5.0, 4.4
>
> Attachments: LUCENE-4986.patch, LUCENE-4986.patch
>
>
> Reported by Reg on the java-user list, subject
> "TrackingIndexWriter.tryDeleteDocument(IndexReader, int) vs
> deleteDocuments(Query)":
> When IW.tryDeleteDocument succeeds, it marks the document as deleted in the
> pending BitVector in ReadersAndLiveDocs, but then when the NRT reader checks
> if it's still current by calling IW.nrtIsCurrent, we fail to catch changes to
> the BitVector, resulting in the NRT reader thinking it's current and not
> reopening.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
