[jira] Resolved: (LUCENE-2634) IndexReader.isCurrent() lies if documents were only removed by latest commit

["Michael McCandless (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless resolved LUCENE-2634.
----------------------------------------

    Fix Version/s: 2.9.4
                   3.0.3
                   3.1
                   4.0
       Resolution: Fixed

> IndexReader.isCurrent() lies if documents were only removed by latest commit
> ----------------------------------------------------------------------------
>
>                 Key: LUCENE-2634
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2634
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 2.9.3
>         Environment: Ubuntu 9.10
> Sun-java-jdk 1.6.0_20-b02
>            Reporter: Nikolay Zamosenchuk
>            Assignee: Michael McCandless
>             Fix For: 2.9.4, 3.0.3, 3.1, 4.0
>
>         Attachments: LUCENE-2634.patch, TestIsCurrent.java
>
>
> Usecase is as following:
> 1. Get indexReader via indexWriter.
> 2. Delete documents by Term via indexWriter. 
> 3. Commit indexWriter.
> 4. indexReader.isCurrent() returns true.
> Usually there is a check if index reader is current. If not then it is reopened (re-obtained via writer or ect.). But this causes the problem when documents can still be found through the search after deletion.
> Testcase is attached.

-- 
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org