You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Victor Hadianto <vi...@nuix.com.au> on 2003/05/02 17:27:15 UTC
High number of files in the index
Hi list,
I'm experiencing a high number of files in the Lucene index, even after
running optimize I still have over 600 files in my Lucene index. Now the
scary thing is that's about the same number of document that I indexed.
This problem didn't happen before, the only change that I can think of is that
I'm changing the documents being indexed. Previously all documents have the
same fields, but now each document has a different set of field indexed.
Is this the problem? Will this cause the high number of files in my index
directory?
Please someone say no .. because otherwise I'm dead.
victor
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: High number of files in the index
Posted by Terry Steichen <te...@net-frame.com>.
What I said (or meant to say) is that the size of the index depends on not
just the number of fields, but also on how many of the fields have their
contents stored in the index. (If, as you state, you don't store any field
contents in the index, this is not an issue with you.)
Terry
----- Original Message -----
From: "Victor Hadianto" <vi...@nuix.com.au>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Monday, May 05, 2003 10:29 PM
Subject: Re: High number of files in the index
> > I believe it's not only the number of fields, but how many fields you
> > select to have their contents included in the index. If you don't need
the
> > content accessible via the index, that can make a big difference.
>
> Hmm so are you saying even if I have a lot of fields as long as they are
not
> stored in the index they are fine? That's strange because all my fields
are
> indexed but not stored in the index. Or perhaps I misunderstood what you
> mean?
>
> > Terry
>
> victor
>
> >
> > ----- Original Message -----
> > From: "Victor Hadianto" <vi...@nuix.com.au>
> > To: "Lucene Users List" <lu...@jakarta.apache.org>
> > Sent: Monday, May 05, 2003 2:10 AM
> > Subject: Re: High number of files in the index
> >
> > > Yes this seems to be the problem. I had to rewrite the indexer and
> >
> > indexing it
> >
> > > a smarter way. Now keeping the number of fields down and the number of
> >
> > files
> >
> > > in the Lucene index to a more acceptable level again.
> > >
> > > victor
> > >
> > > On Mon, 5 May 2003 03:58 pm, Sushma Sinha wrote:
> > > > The most obvious reason seems to be the increase in number of
fields.
> > > > I guess lucene creates one file for each field in the index.
> > > > You can check by looking at the file names in the index, if you have
N
> > > > number of files with the common prefix ,
> > > > but different suffix , those are all created for different fields.
> > > >
> > > > And also , is the lucene performance affected by the no of files in
the
> > > > index. I think u can look at the index size as a whole
> > > > And if it affects the performance, is there a way to merge the files
> > > > and
> >
> > do
> >
> > > > further optimization?.. as I have not much info about the additional
> >
> > files
> >
> > > > created in the index.
> > > >
> > > > - Sushma
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Victor Hadianto" <vi...@nuix.com.au>
> > > > To: "Lucene Users List" <lu...@jakarta.apache.org>
> > > > Sent: Friday, May 02, 2003 8:57 PM
> > > > Subject: High number of files in the index
> > > >
> > > > > Hi list,
> > > > >
> > > > > I'm experiencing a high number of files in the Lucene index, even
> >
> > after
> >
> > > > > running optimize I still have over 600 files in my Lucene index.
Now
> >
> > the
> >
> > > > > scary thing is that's about the same number of document that I
> >
> > indexed.
> >
> > > > > This problem didn't happen before, the only change that I can
think
> > > > > of
> >
> > is
> >
> > > > that
> > > >
> > > > > I'm changing the documents being indexed. Previously all documents
> >
> > have
> >
> > > > the
> > > >
> > > > > same fields, but now each document has a different set of field
> >
> > indexed.
> >
> > > > > Is this the problem? Will this cause the high number of files in
my
> >
> > index
> >
> > > > > directory?
> > > > >
> > > > > Please someone say no .. because otherwise I'm dead.
> > > > >
> > > > >
> > > > > victor
> > > > >
> > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > > > > For additional commands, e-mail:
lucene-user-help@jakarta.apache.org
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> > >
> > > --
> > > Victor Hadianto
> > >
> > > NUIX Pty Ltd
> > > Level 8, 143 York Street, Sydney 2000
> > > Phone: (02) 9283 9010
> > > Fax: (02) 9283 9020
> > >
> > > This message is intended only for the named recipient. If you are not
the
> > > intended recipient you are notified that disclosing, copying,
> > > distributing or taking any action in reliance on the contents of this
> > > message or attachment is strictly prohibited.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: High number of files in the index
Posted by Victor Hadianto <vi...@nuix.com.au>.
> I believe it's not only the number of fields, but how many fields you
> select to have their contents included in the index. If you don't need the
> content accessible via the index, that can make a big difference.
Hmm so are you saying even if I have a lot of fields as long as they are not
stored in the index they are fine? That's strange because all my fields are
indexed but not stored in the index. Or perhaps I misunderstood what you
mean?
> Terry
victor
>
> ----- Original Message -----
> From: "Victor Hadianto" <vi...@nuix.com.au>
> To: "Lucene Users List" <lu...@jakarta.apache.org>
> Sent: Monday, May 05, 2003 2:10 AM
> Subject: Re: High number of files in the index
>
> > Yes this seems to be the problem. I had to rewrite the indexer and
>
> indexing it
>
> > a smarter way. Now keeping the number of fields down and the number of
>
> files
>
> > in the Lucene index to a more acceptable level again.
> >
> > victor
> >
> > On Mon, 5 May 2003 03:58 pm, Sushma Sinha wrote:
> > > The most obvious reason seems to be the increase in number of fields.
> > > I guess lucene creates one file for each field in the index.
> > > You can check by looking at the file names in the index, if you have N
> > > number of files with the common prefix ,
> > > but different suffix , those are all created for different fields.
> > >
> > > And also , is the lucene performance affected by the no of files in the
> > > index. I think u can look at the index size as a whole
> > > And if it affects the performance, is there a way to merge the files
> > > and
>
> do
>
> > > further optimization?.. as I have not much info about the additional
>
> files
>
> > > created in the index.
> > >
> > > - Sushma
> > >
> > >
> > > ----- Original Message -----
> > > From: "Victor Hadianto" <vi...@nuix.com.au>
> > > To: "Lucene Users List" <lu...@jakarta.apache.org>
> > > Sent: Friday, May 02, 2003 8:57 PM
> > > Subject: High number of files in the index
> > >
> > > > Hi list,
> > > >
> > > > I'm experiencing a high number of files in the Lucene index, even
>
> after
>
> > > > running optimize I still have over 600 files in my Lucene index. Now
>
> the
>
> > > > scary thing is that's about the same number of document that I
>
> indexed.
>
> > > > This problem didn't happen before, the only change that I can think
> > > > of
>
> is
>
> > > that
> > >
> > > > I'm changing the documents being indexed. Previously all documents
>
> have
>
> > > the
> > >
> > > > same fields, but now each document has a different set of field
>
> indexed.
>
> > > > Is this the problem? Will this cause the high number of files in my
>
> index
>
> > > > directory?
> > > >
> > > > Please someone say no .. because otherwise I'm dead.
> > > >
> > > >
> > > > victor
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> >
> > --
> > Victor Hadianto
> >
> > NUIX Pty Ltd
> > Level 8, 143 York Street, Sydney 2000
> > Phone: (02) 9283 9010
> > Fax: (02) 9283 9020
> >
> > This message is intended only for the named recipient. If you are not the
> > intended recipient you are notified that disclosing, copying,
> > distributing or taking any action in reliance on the contents of this
> > message or attachment is strictly prohibited.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: IndexReader.lastModified();
Posted by Tatu Saloranta <ta...@hypermall.net>.
On Tuesday 06 May 2003 05:42, Rob Outar wrote:
> Yeah it looks like I am going to have to handle it internally instead of
> relying on IndexReader.lastModified(), oh well so much for
> cross-platform-ism :-)
[regarding ext2-fs 'feature' on Linux]
I think this 'feature' might be useful thing to document in a FAQ. Perhaps
there should be a platform-dependancies FAQ (or sub-section). Wasn't there
also some concern regarding Windows platform, where deleted status of a file
was not reliably accessed by Java (or something similar)?
Also, do you think ext3 has same problem? (or if it has, other new journaling
file systems).
-+ Tatu +-
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
RE: IndexReader.lastModified();
Posted by Rob Outar <ro...@ideorlando.org>.
Yeah it looks like I am going to have to handle it internally instead of
relying on IndexReader.lastModified(), oh well so much for
cross-platform-ism :-)
Thanks,
Rob
-----Original Message-----
From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
Sent: Monday, May 05, 2003 4:12 PM
To: Lucene Users List
Subject: RE: IndexReader.lastModified();
Oh, I see what you mean. You are talking about the delta between the
original time stamp, and the time stamp that you expect after you add a
document. I thought you were saying that it takes the F/S at least a
second to update the time stamp, after the file has been modified.
In that case, this is a file system issue that Lucene can't do much
about.
Otis
--- Rob Outar <ro...@ideorlando.org> wrote:
> We looked it up on Goggle, ext2 file system does not update the last
> mod
> date if the change to the file is under 1 second. Also I don't
> remember
> cause my brain hurts, when Linux returned the time it did not include
> ms,
> but on Windows it did, all my queries on Windows worked because of
> this.
>
> A sleep does not work, it is the modification time, of the file, not
> how
> long the test takes.
>
> Thanks,
>
> Rob
>
>
> -----Original Message-----
> From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
> Sent: Monday, May 05, 2003 3:53 PM
> To: Lucene Users List
> Subject: RE: IndexReader.lastModified();
>
>
> I wouldn't trust that < 1 second statement :)
> Just put a sleep in your unit test and see.
>
> Otis
>
> --- Rob Outar <ro...@ideorlando.org> wrote:
> > My Linux admin told me that if a change to a file occurs in less
> than
> > one
> > second Linux does not update the last mod date. Has anyone else
> > experienced
> > this? or is this even possible? I have spent hours and hours
> > debugging my
> > code and the date thing is the only thing I can see as causing my
> > queries to
> > fail.
> >
> >
> > Thanks,
> >
> > Rob
> >
> >
> > -----Original Message-----
> > From: Rob Outar [mailto:routar@ideorlando.org]
> > Sent: Monday, May 05, 2003 2:42 PM
> > To: Lucene Users List
> > Subject: RE: IndexReader.lastModified();
> >
> >
> > /** Returns the time the index in the named directory was last
> > modified.
> > */
> > public static long lastModified(File directory) throws
> IOException
> > {
> > return FSDirectory.fileModified(directory, "segments");
> > }
> >
> > /** Returns the time the named file was last modified. */
> > public final long fileModified(String name) throws IOException {
> > File file = new File(directory, name);
> > return file.lastModified();
> > }
> >
> > /** Returns the time the named file was last modified. */
> > public static final long fileModified(File directory, String
> name)
> > throws IOException {
> > File file = new File(directory, name);
> > return file.lastModified();
> > }
> >
> > Could this be a problem in Linux where the files last mod date are
> > not being
> > updated fast enough?
> >
> > Thanks,
> >
> > Rob Outar
> > OneSAF A&I -- SAIC
> > Software\Data Engineer
> > 321-235-7660
> > outarr@saic.com <ma...@saic.com>
> >
> >
> > -----Original Message-----
> > From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
> > Sent: Monday, May 05, 2003 2:37 PM
> > To: Lucene Users List
> > Subject: Re: IndexReader.lastModified();
> >
> >
> > I don't remember any more, but maybe lastModified() returns a new
> > value
> > only after the IndexWriter is close()d. You may be able to tell
> from
> > looking at the source.... or you should just try that and see.
> >
> > Otis
> >
> >
> > --- Rob Outar <ro...@ideorlando.org> wrote:
> > > Hi all,
> > >
> > > I am experiencing a weird problem in Linux. When I initially
> > create
> > > the
> > > index I store the date with the IndexReader.lastModified() call.
> I
> > > then
> > > have a Junit test that adds a document to the index, I then have
> a
> > > method
> > > that checks if the index has changed and if it has I create a new
> > > IndexSearcher. The problem is the date the index was created and
> > the
> > > most
> > > recent call to IndexReader.lastModified()(after adding a
> document)
> > > are
> > > returning the same value so when I query on the new document I
> just
> > > added it
> > > is failing because according to the dates, the index has not
> > changed
> > > so I
> > > did not create a new IndexSearcher!!!
> > >
> > > Has anyone experience this before? If so, is there a known fix?
> > >
> > > Thanks,
> > >
> > > Rob
> > >
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> lucene-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> > lucene-user-help@jakarta.apache.org
> > >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo.
> > http://search.yahoo.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> lucene-user-help@jakarta.apache.org
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> lucene-user-help@jakarta.apache.org
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> lucene-user-help@jakarta.apache.org
> >
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
RE: IndexReader.lastModified();
Posted by Otis Gospodnetic <ot...@yahoo.com>.
Oh, I see what you mean. You are talking about the delta between the
original time stamp, and the time stamp that you expect after you add a
document. I thought you were saying that it takes the F/S at least a
second to update the time stamp, after the file has been modified.
In that case, this is a file system issue that Lucene can't do much
about.
Otis
--- Rob Outar <ro...@ideorlando.org> wrote:
> We looked it up on Goggle, ext2 file system does not update the last
> mod
> date if the change to the file is under 1 second. Also I don't
> remember
> cause my brain hurts, when Linux returned the time it did not include
> ms,
> but on Windows it did, all my queries on Windows worked because of
> this.
>
> A sleep does not work, it is the modification time, of the file, not
> how
> long the test takes.
>
> Thanks,
>
> Rob
>
>
> -----Original Message-----
> From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
> Sent: Monday, May 05, 2003 3:53 PM
> To: Lucene Users List
> Subject: RE: IndexReader.lastModified();
>
>
> I wouldn't trust that < 1 second statement :)
> Just put a sleep in your unit test and see.
>
> Otis
>
> --- Rob Outar <ro...@ideorlando.org> wrote:
> > My Linux admin told me that if a change to a file occurs in less
> than
> > one
> > second Linux does not update the last mod date. Has anyone else
> > experienced
> > this? or is this even possible? I have spent hours and hours
> > debugging my
> > code and the date thing is the only thing I can see as causing my
> > queries to
> > fail.
> >
> >
> > Thanks,
> >
> > Rob
> >
> >
> > -----Original Message-----
> > From: Rob Outar [mailto:routar@ideorlando.org]
> > Sent: Monday, May 05, 2003 2:42 PM
> > To: Lucene Users List
> > Subject: RE: IndexReader.lastModified();
> >
> >
> > /** Returns the time the index in the named directory was last
> > modified.
> > */
> > public static long lastModified(File directory) throws
> IOException
> > {
> > return FSDirectory.fileModified(directory, "segments");
> > }
> >
> > /** Returns the time the named file was last modified. */
> > public final long fileModified(String name) throws IOException {
> > File file = new File(directory, name);
> > return file.lastModified();
> > }
> >
> > /** Returns the time the named file was last modified. */
> > public static final long fileModified(File directory, String
> name)
> > throws IOException {
> > File file = new File(directory, name);
> > return file.lastModified();
> > }
> >
> > Could this be a problem in Linux where the files last mod date are
> > not being
> > updated fast enough?
> >
> > Thanks,
> >
> > Rob Outar
> > OneSAF A&I -- SAIC
> > Software\Data Engineer
> > 321-235-7660
> > outarr@saic.com <ma...@saic.com>
> >
> >
> > -----Original Message-----
> > From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
> > Sent: Monday, May 05, 2003 2:37 PM
> > To: Lucene Users List
> > Subject: Re: IndexReader.lastModified();
> >
> >
> > I don't remember any more, but maybe lastModified() returns a new
> > value
> > only after the IndexWriter is close()d. You may be able to tell
> from
> > looking at the source.... or you should just try that and see.
> >
> > Otis
> >
> >
> > --- Rob Outar <ro...@ideorlando.org> wrote:
> > > Hi all,
> > >
> > > I am experiencing a weird problem in Linux. When I initially
> > create
> > > the
> > > index I store the date with the IndexReader.lastModified() call.
> I
> > > then
> > > have a Junit test that adds a document to the index, I then have
> a
> > > method
> > > that checks if the index has changed and if it has I create a new
> > > IndexSearcher. The problem is the date the index was created and
> > the
> > > most
> > > recent call to IndexReader.lastModified()(after adding a
> document)
> > > are
> > > returning the same value so when I query on the new document I
> just
> > > added it
> > > is failing because according to the dates, the index has not
> > changed
> > > so I
> > > did not create a new IndexSearcher!!!
> > >
> > > Has anyone experience this before? If so, is there a known fix?
> > >
> > > Thanks,
> > >
> > > Rob
> > >
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> lucene-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> > lucene-user-help@jakarta.apache.org
> > >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo.
> > http://search.yahoo.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> lucene-user-help@jakarta.apache.org
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> lucene-user-help@jakarta.apache.org
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> lucene-user-help@jakarta.apache.org
> >
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
RE: IndexReader.lastModified();
Posted by Rob Outar <ro...@ideorlando.org>.
We looked it up on Goggle, ext2 file system does not update the last mod
date if the change to the file is under 1 second. Also I don't remember
cause my brain hurts, when Linux returned the time it did not include ms,
but on Windows it did, all my queries on Windows worked because of this.
A sleep does not work, it is the modification time, of the file, not how
long the test takes.
Thanks,
Rob
-----Original Message-----
From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
Sent: Monday, May 05, 2003 3:53 PM
To: Lucene Users List
Subject: RE: IndexReader.lastModified();
I wouldn't trust that < 1 second statement :)
Just put a sleep in your unit test and see.
Otis
--- Rob Outar <ro...@ideorlando.org> wrote:
> My Linux admin told me that if a change to a file occurs in less than
> one
> second Linux does not update the last mod date. Has anyone else
> experienced
> this? or is this even possible? I have spent hours and hours
> debugging my
> code and the date thing is the only thing I can see as causing my
> queries to
> fail.
>
>
> Thanks,
>
> Rob
>
>
> -----Original Message-----
> From: Rob Outar [mailto:routar@ideorlando.org]
> Sent: Monday, May 05, 2003 2:42 PM
> To: Lucene Users List
> Subject: RE: IndexReader.lastModified();
>
>
> /** Returns the time the index in the named directory was last
> modified.
> */
> public static long lastModified(File directory) throws IOException
> {
> return FSDirectory.fileModified(directory, "segments");
> }
>
> /** Returns the time the named file was last modified. */
> public final long fileModified(String name) throws IOException {
> File file = new File(directory, name);
> return file.lastModified();
> }
>
> /** Returns the time the named file was last modified. */
> public static final long fileModified(File directory, String name)
> throws IOException {
> File file = new File(directory, name);
> return file.lastModified();
> }
>
> Could this be a problem in Linux where the files last mod date are
> not being
> updated fast enough?
>
> Thanks,
>
> Rob Outar
> OneSAF A&I -- SAIC
> Software\Data Engineer
> 321-235-7660
> outarr@saic.com <ma...@saic.com>
>
>
> -----Original Message-----
> From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
> Sent: Monday, May 05, 2003 2:37 PM
> To: Lucene Users List
> Subject: Re: IndexReader.lastModified();
>
>
> I don't remember any more, but maybe lastModified() returns a new
> value
> only after the IndexWriter is close()d. You may be able to tell from
> looking at the source.... or you should just try that and see.
>
> Otis
>
>
> --- Rob Outar <ro...@ideorlando.org> wrote:
> > Hi all,
> >
> > I am experiencing a weird problem in Linux. When I initially
> create
> > the
> > index I store the date with the IndexReader.lastModified() call. I
> > then
> > have a Junit test that adds a document to the index, I then have a
> > method
> > that checks if the index has changed and if it has I create a new
> > IndexSearcher. The problem is the date the index was created and
> the
> > most
> > recent call to IndexReader.lastModified()(after adding a document)
> > are
> > returning the same value so when I query on the new document I just
> > added it
> > is failing because according to the dates, the index has not
> changed
> > so I
> > did not create a new IndexSearcher!!!
> >
> > Has anyone experience this before? If so, is there a known fix?
> >
> > Thanks,
> >
> > Rob
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> lucene-user-help@jakarta.apache.org
> >
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
RE: IndexReader.lastModified();
Posted by Otis Gospodnetic <ot...@yahoo.com>.
I wouldn't trust that < 1 second statement :)
Just put a sleep in your unit test and see.
Otis
--- Rob Outar <ro...@ideorlando.org> wrote:
> My Linux admin told me that if a change to a file occurs in less than
> one
> second Linux does not update the last mod date. Has anyone else
> experienced
> this? or is this even possible? I have spent hours and hours
> debugging my
> code and the date thing is the only thing I can see as causing my
> queries to
> fail.
>
>
> Thanks,
>
> Rob
>
>
> -----Original Message-----
> From: Rob Outar [mailto:routar@ideorlando.org]
> Sent: Monday, May 05, 2003 2:42 PM
> To: Lucene Users List
> Subject: RE: IndexReader.lastModified();
>
>
> /** Returns the time the index in the named directory was last
> modified.
> */
> public static long lastModified(File directory) throws IOException
> {
> return FSDirectory.fileModified(directory, "segments");
> }
>
> /** Returns the time the named file was last modified. */
> public final long fileModified(String name) throws IOException {
> File file = new File(directory, name);
> return file.lastModified();
> }
>
> /** Returns the time the named file was last modified. */
> public static final long fileModified(File directory, String name)
> throws IOException {
> File file = new File(directory, name);
> return file.lastModified();
> }
>
> Could this be a problem in Linux where the files last mod date are
> not being
> updated fast enough?
>
> Thanks,
>
> Rob Outar
> OneSAF A&I -- SAIC
> Software\Data Engineer
> 321-235-7660
> outarr@saic.com <ma...@saic.com>
>
>
> -----Original Message-----
> From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
> Sent: Monday, May 05, 2003 2:37 PM
> To: Lucene Users List
> Subject: Re: IndexReader.lastModified();
>
>
> I don't remember any more, but maybe lastModified() returns a new
> value
> only after the IndexWriter is close()d. You may be able to tell from
> looking at the source.... or you should just try that and see.
>
> Otis
>
>
> --- Rob Outar <ro...@ideorlando.org> wrote:
> > Hi all,
> >
> > I am experiencing a weird problem in Linux. When I initially
> create
> > the
> > index I store the date with the IndexReader.lastModified() call. I
> > then
> > have a Junit test that adds a document to the index, I then have a
> > method
> > that checks if the index has changed and if it has I create a new
> > IndexSearcher. The problem is the date the index was created and
> the
> > most
> > recent call to IndexReader.lastModified()(after adding a document)
> > are
> > returning the same value so when I query on the new document I just
> > added it
> > is failing because according to the dates, the index has not
> changed
> > so I
> > did not create a new IndexSearcher!!!
> >
> > Has anyone experience this before? If so, is there a known fix?
> >
> > Thanks,
> >
> > Rob
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> lucene-user-help@jakarta.apache.org
> >
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
RE: IndexReader.lastModified();
Posted by Rob Outar <ro...@ideorlando.org>.
My Linux admin told me that if a change to a file occurs in less than one
second Linux does not update the last mod date. Has anyone else experienced
this? or is this even possible? I have spent hours and hours debugging my
code and the date thing is the only thing I can see as causing my queries to
fail.
Thanks,
Rob
-----Original Message-----
From: Rob Outar [mailto:routar@ideorlando.org]
Sent: Monday, May 05, 2003 2:42 PM
To: Lucene Users List
Subject: RE: IndexReader.lastModified();
/** Returns the time the index in the named directory was last modified.
*/
public static long lastModified(File directory) throws IOException {
return FSDirectory.fileModified(directory, "segments");
}
/** Returns the time the named file was last modified. */
public final long fileModified(String name) throws IOException {
File file = new File(directory, name);
return file.lastModified();
}
/** Returns the time the named file was last modified. */
public static final long fileModified(File directory, String name)
throws IOException {
File file = new File(directory, name);
return file.lastModified();
}
Could this be a problem in Linux where the files last mod date are not being
updated fast enough?
Thanks,
Rob Outar
OneSAF A&I -- SAIC
Software\Data Engineer
321-235-7660
outarr@saic.com <ma...@saic.com>
-----Original Message-----
From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
Sent: Monday, May 05, 2003 2:37 PM
To: Lucene Users List
Subject: Re: IndexReader.lastModified();
I don't remember any more, but maybe lastModified() returns a new value
only after the IndexWriter is close()d. You may be able to tell from
looking at the source.... or you should just try that and see.
Otis
--- Rob Outar <ro...@ideorlando.org> wrote:
> Hi all,
>
> I am experiencing a weird problem in Linux. When I initially create
> the
> index I store the date with the IndexReader.lastModified() call. I
> then
> have a Junit test that adds a document to the index, I then have a
> method
> that checks if the index has changed and if it has I create a new
> IndexSearcher. The problem is the date the index was created and the
> most
> recent call to IndexReader.lastModified()(after adding a document)
> are
> returning the same value so when I query on the new document I just
> added it
> is failing because according to the dates, the index has not changed
> so I
> did not create a new IndexSearcher!!!
>
> Has anyone experience this before? If so, is there a known fix?
>
> Thanks,
>
> Rob
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
RE: IndexReader.lastModified();
Posted by Rob Outar <ro...@ideorlando.org>.
/** Returns the time the index in the named directory was last modified.
*/
public static long lastModified(File directory) throws IOException {
return FSDirectory.fileModified(directory, "segments");
}
/** Returns the time the named file was last modified. */
public final long fileModified(String name) throws IOException {
File file = new File(directory, name);
return file.lastModified();
}
/** Returns the time the named file was last modified. */
public static final long fileModified(File directory, String name)
throws IOException {
File file = new File(directory, name);
return file.lastModified();
}
Could this be a problem in Linux where the files last mod date are not being
updated fast enough?
Thanks,
Rob Outar
OneSAF A&I -- SAIC
Software\Data Engineer
321-235-7660
outarr@saic.com <ma...@saic.com>
-----Original Message-----
From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
Sent: Monday, May 05, 2003 2:37 PM
To: Lucene Users List
Subject: Re: IndexReader.lastModified();
I don't remember any more, but maybe lastModified() returns a new value
only after the IndexWriter is close()d. You may be able to tell from
looking at the source.... or you should just try that and see.
Otis
--- Rob Outar <ro...@ideorlando.org> wrote:
> Hi all,
>
> I am experiencing a weird problem in Linux. When I initially create
> the
> index I store the date with the IndexReader.lastModified() call. I
> then
> have a Junit test that adds a document to the index, I then have a
> method
> that checks if the index has changed and if it has I create a new
> IndexSearcher. The problem is the date the index was created and the
> most
> recent call to IndexReader.lastModified()(after adding a document)
> are
> returning the same value so when I query on the new document I just
> added it
> is failing because according to the dates, the index has not changed
> so I
> did not create a new IndexSearcher!!!
>
> Has anyone experience this before? If so, is there a known fix?
>
> Thanks,
>
> Rob
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: IndexReader.lastModified();
Posted by Otis Gospodnetic <ot...@yahoo.com>.
I don't remember any more, but maybe lastModified() returns a new value
only after the IndexWriter is close()d. You may be able to tell from
looking at the source.... or you should just try that and see.
Otis
--- Rob Outar <ro...@ideorlando.org> wrote:
> Hi all,
>
> I am experiencing a weird problem in Linux. When I initially create
> the
> index I store the date with the IndexReader.lastModified() call. I
> then
> have a Junit test that adds a document to the index, I then have a
> method
> that checks if the index has changed and if it has I create a new
> IndexSearcher. The problem is the date the index was created and the
> most
> recent call to IndexReader.lastModified()(after adding a document)
> are
> returning the same value so when I query on the new document I just
> added it
> is failing because according to the dates, the index has not changed
> so I
> did not create a new IndexSearcher!!!
>
> Has anyone experience this before? If so, is there a known fix?
>
> Thanks,
>
> Rob
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
IndexReader.lastModified();
Posted by Rob Outar <ro...@ideorlando.org>.
Hi all,
I am experiencing a weird problem in Linux. When I initially create the
index I store the date with the IndexReader.lastModified() call. I then
have a Junit test that adds a document to the index, I then have a method
that checks if the index has changed and if it has I create a new
IndexSearcher. The problem is the date the index was created and the most
recent call to IndexReader.lastModified()(after adding a document) are
returning the same value so when I query on the new document I just added it
is failing because according to the dates, the index has not changed so I
did not create a new IndexSearcher!!!
Has anyone experience this before? If so, is there a known fix?
Thanks,
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: High number of files in the index
Posted by Terry Steichen <te...@net-frame.com>.
Victor,
I believe it's not only the number of fields, but how many fields you select
to have their contents included in the index. If you don't need the content
accessible via the index, that can make a big difference.
HTH,
Terry
----- Original Message -----
From: "Victor Hadianto" <vi...@nuix.com.au>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Monday, May 05, 2003 2:10 AM
Subject: Re: High number of files in the index
> Yes this seems to be the problem. I had to rewrite the indexer and
indexing it
> a smarter way. Now keeping the number of fields down and the number of
files
> in the Lucene index to a more acceptable level again.
>
> victor
>
> On Mon, 5 May 2003 03:58 pm, Sushma Sinha wrote:
> > The most obvious reason seems to be the increase in number of fields.
> > I guess lucene creates one file for each field in the index.
> > You can check by looking at the file names in the index, if you have N
> > number of files with the common prefix ,
> > but different suffix , those are all created for different fields.
> >
> > And also , is the lucene performance affected by the no of files in the
> > index. I think u can look at the index size as a whole
> > And if it affects the performance, is there a way to merge the files and
do
> > further optimization?.. as I have not much info about the additional
files
> > created in the index.
> >
> > - Sushma
> >
> >
> > ----- Original Message -----
> > From: "Victor Hadianto" <vi...@nuix.com.au>
> > To: "Lucene Users List" <lu...@jakarta.apache.org>
> > Sent: Friday, May 02, 2003 8:57 PM
> > Subject: High number of files in the index
> >
> > > Hi list,
> > >
> > > I'm experiencing a high number of files in the Lucene index, even
after
> > > running optimize I still have over 600 files in my Lucene index. Now
the
> > > scary thing is that's about the same number of document that I
indexed.
> > >
> > > This problem didn't happen before, the only change that I can think of
is
> >
> > that
> >
> > > I'm changing the documents being indexed. Previously all documents
have
> >
> > the
> >
> > > same fields, but now each document has a different set of field
indexed.
> > >
> > > Is this the problem? Will this cause the high number of files in my
index
> > > directory?
> > >
> > > Please someone say no .. because otherwise I'm dead.
> > >
> > >
> > > victor
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
> --
> Victor Hadianto
>
> NUIX Pty Ltd
> Level 8, 143 York Street, Sydney 2000
> Phone: (02) 9283 9010
> Fax: (02) 9283 9020
>
> This message is intended only for the named recipient. If you are not the
> intended recipient you are notified that disclosing, copying, distributing
> or taking any action in reliance on the contents of this message or
> attachment is strictly prohibited.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: High number of files in the index
Posted by Victor Hadianto <vi...@nuix.com.au>.
Yes this seems to be the problem. I had to rewrite the indexer and indexing it
a smarter way. Now keeping the number of fields down and the number of files
in the Lucene index to a more acceptable level again.
victor
On Mon, 5 May 2003 03:58 pm, Sushma Sinha wrote:
> The most obvious reason seems to be the increase in number of fields.
> I guess lucene creates one file for each field in the index.
> You can check by looking at the file names in the index, if you have N
> number of files with the common prefix ,
> but different suffix , those are all created for different fields.
>
> And also , is the lucene performance affected by the no of files in the
> index. I think u can look at the index size as a whole
> And if it affects the performance, is there a way to merge the files and do
> further optimization?.. as I have not much info about the additional files
> created in the index.
>
> - Sushma
>
>
> ----- Original Message -----
> From: "Victor Hadianto" <vi...@nuix.com.au>
> To: "Lucene Users List" <lu...@jakarta.apache.org>
> Sent: Friday, May 02, 2003 8:57 PM
> Subject: High number of files in the index
>
> > Hi list,
> >
> > I'm experiencing a high number of files in the Lucene index, even after
> > running optimize I still have over 600 files in my Lucene index. Now the
> > scary thing is that's about the same number of document that I indexed.
> >
> > This problem didn't happen before, the only change that I can think of is
>
> that
>
> > I'm changing the documents being indexed. Previously all documents have
>
> the
>
> > same fields, but now each document has a different set of field indexed.
> >
> > Is this the problem? Will this cause the high number of files in my index
> > directory?
> >
> > Please someone say no .. because otherwise I'm dead.
> >
> >
> > victor
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
--
Victor Hadianto
NUIX Pty Ltd
Level 8, 143 York Street, Sydney 2000
Phone: (02) 9283 9010
Fax: (02) 9283 9020
This message is intended only for the named recipient. If you are not the
intended recipient you are notified that disclosing, copying, distributing
or taking any action in reliance on the contents of this message or
attachment is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: High number of files in the index
Posted by Sushma Sinha <su...@translogicsys.com>.
The most obvious reason seems to be the increase in number of fields.
I guess lucene creates one file for each field in the index.
You can check by looking at the file names in the index, if you have N
number of files with the common prefix ,
but different suffix , those are all created for different fields.
And also , is the lucene performance affected by the no of files in the
index. I think u can look at the index size as a whole
And if it affects the performance, is there a way to merge the files and do
further optimization?.. as I have not much info about the additional files
created in the index.
- Sushma
----- Original Message -----
From: "Victor Hadianto" <vi...@nuix.com.au>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Friday, May 02, 2003 8:57 PM
Subject: High number of files in the index
> Hi list,
>
> I'm experiencing a high number of files in the Lucene index, even after
> running optimize I still have over 600 files in my Lucene index. Now the
> scary thing is that's about the same number of document that I indexed.
>
> This problem didn't happen before, the only change that I can think of is
that
> I'm changing the documents being indexed. Previously all documents have
the
> same fields, but now each document has a different set of field indexed.
>
> Is this the problem? Will this cause the high number of files in my index
> directory?
>
> Please someone say no .. because otherwise I'm dead.
>
>
> victor
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
RE: High number of files in the index
Posted by Aviran Mordo <am...@infosciences.com>.
AFAIK the number of files depends among other things on the number of
fields.
Aviran
-----Original Message-----
From: Victor Hadianto [mailto:victorh@nuix.com.au]
Sent: Friday, May 02, 2003 11:27 AM
To: Lucene Users List
Subject: High number of files in the index
Hi list,
I'm experiencing a high number of files in the Lucene index, even after
running optimize I still have over 600 files in my Lucene index. Now the
scary thing is that's about the same number of document that I indexed.
This problem didn't happen before, the only change that I can think of
is that
I'm changing the documents being indexed. Previously all documents have
the
same fields, but now each document has a different set of field indexed.
Is this the problem? Will this cause the high number of files in my
index
directory?
Please someone say no .. because otherwise I'm dead.
victor
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org