Re: isCurrent says no, but contents still invisible

2007-01-10 Thread Doron Cohen
That's strange. Since you don't close the writer usually adding the doc would not modify the index (unless adding the doc triggered a merge). You may want to check that: 1. writer and reader really opened against the same path; 2. reader isCurrent state also before adding the doc and after

RE: isCurrent says no, but contents still invisible

2007-01-10 Thread Benson Margulies
: Re: isCurrent says no, but contents still invisible That's strange. Since you don't close the writer usually adding the doc would not modify the index (unless adding the doc triggered a merge). You may want to check that: 1. writer and reader really opened against the same path; 2. reader

Re: isCurrent says no, but contents still invisible

2007-01-10 Thread Erick Erickson
, and slink away. -Original Message- From: Doron Cohen [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:07 PM To: java-user@lucene.apache.org Subject: Re: isCurrent says no, but contents still invisible That's strange. Since you don't close the writer usually adding the doc

RE: isCurrent says no, but contents still invisible

2007-01-10 Thread Benson Margulies
Yea, that part I got. -Original Message- From: Erick Erickson [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 5:22 PM To: java-user@lucene.apache.org Subject: Re: isCurrent says no, but contents still invisible And don't forget that you need to close and re-open the reader

RE: isCurrent says no, but contents still invisible

2007-01-10 Thread Benson Margulies
To: java-user@lucene.apache.org Subject: Re: isCurrent says no, but contents still invisible And don't forget that you need to close and re-open the reader to pick up the changes... [EMAIL PROTECTED] G. On 1/10/07, Benson Margulies [EMAIL PROTECTED] wrote: #2 is a possible issue. I stared

RE: isCurrent says no, but contents still invisible

2007-01-10 Thread Doron Cohen
Benson Margulies [EMAIL PROTECTED] wrote on 10/01/2007 14:26:42: Oh, boy, what a mistake. I thought I was being clever by creating a Directory object. All that did was prevent the writer from ever quite flushing because I wasn't closing THAT. No need to close the directory object for that.

RE: isCurrent says no, but contents still invisible

2007-01-10 Thread Benson Margulies
If all is well with the lifecycle, should IndexReader.numDocs() return an accurate count? -Original Message- From: Doron Cohen [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 5:54 PM To: java-user@lucene.apache.org Subject: RE: isCurrent says no, but contents still

RE: isCurrent says no, but contents still invisible

2007-01-10 Thread Benson Margulies
OK, all is well. I had a truly embarrassing logic error that I introduced while getting all the closing and opening straightened out. Thanks for the patience. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,