Thanks, ya' learn something new every day <G>. Also, I hadn't seen the other responses, coffee hadn't kicked in.
Erick On Wed, Sep 8, 2010 at 8:30 AM, Michael McCandless < [email protected]> wrote: > Actually, IR.isCurrent() is supposed to return false if any changes > have been committed to the index since the IR was opened. > > Mike > > On Wed, Sep 8, 2010 at 8:11 AM, Erick Erickson <[email protected]> > wrote: > > I'd expect this behavior if you haven't re-opened your underlying > > readers after the commit. No index changes are visible after > > a reader has been opened. > > > > Your steps to reproduce do not show any reopen, what happens > > when you do? > > > > Best > > Erick > > > > On Wed, Sep 8, 2010 at 3:54 AM, Nikolay Zamosenchuk (JIRA) > > <[email protected]>wrote: > > > >> 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 > >> > >> > >> 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: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > I'd expect this behavior if you haven't re-opened your underlying > > readers after the commit. No index changes are visible after > > a reader has been opened. > > Your steps to reproduce do not show any reopen, what happens > > when you do? > > Best > > Erick > > > > On Wed, Sep 8, 2010 at 3:54 AM, Nikolay Zamosenchuk (JIRA) < > [email protected]> wrote: > >> > >> 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 > >> > >> > >> 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: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
