[jira] [Updated] (LUCENE-4986) NRT reader doesn't see changes after successful IW.tryDeleteDocument
[ https://issues.apache.org/jira/browse/LUCENE-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated LUCENE-4986: -- Fix Version/s: (was: 4.4) 4.3.1 Labels: (was: lucene-4.3.1-candidate) Back ported to 4.3.1 r1483358. I had to change the TestTryDelete test to use NRTManager.TrackingIndexWriter because TrackingIndexWriter only became an independent class since LUCENE-4967 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.3.1 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4986) NRT reader doesn't see changes after successful IW.tryDeleteDocument
[ https://issues.apache.org/jira/browse/LUCENE-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated LUCENE-4986: --- Labels: lucene-4.3.1-candidate (was: ) 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 Labels: lucene-4.3.1-candidate 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4986) NRT reader doesn't see changes after successful IW.tryDeleteDocument
[ https://issues.apache.org/jira/browse/LUCENE-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-4986: --- Attachment: LUCENE-4986.patch Patch with test case showing the failure, from Reg (I tweaked it a bit to adapt to trunk APIs). I think to fix this, the NRT reader should also (only?) track the changeCount that IndexWriter uses. 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 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-4986) NRT reader doesn't see changes after successful IW.tryDeleteDocument
[ https://issues.apache.org/jira/browse/LUCENE-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-4986: --- Attachment: LUCENE-4986.patch Patch w/ fix, plus some cleanup in StandardDirectoryReader ... I think it's ready. 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
