lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "hui" <...@triplehop.com>
Subject RE: Sys properties Was: java.io.tmpdir as lock dir .... once again
Date Wed, 03 Mar 2004 21:25:38 GMT
Anoterh similar issue. If we could have a parameter to control the max
number of the files within the index, that is going to avoid the problem of
running of the file handler issue.
When the file number within one index reaches the limit, optimization is
going to be called.
Right now, if the file number within one index out of the limit of your
window system, you lost the index.
Thank you for the consideration.

Regards,
hui

-----Original Message-----
From: Doug Cutting [mailto:cutting@apache.org] 
Sent: Wednesday, March 03, 2004 3:46 PM
To: Lucene Users List
Subject: Re: Sys properties Was: java.io.tmpdir as lock dir .... once again

Stephane James Vaucher wrote:
> As I've stated in my earlier mail, I like this change. More importantly, 
> could this become a "standard" way of changing configurations at runtime? 
> For example, the default merge factor could also be set in this manner.

Sure, that's reasonable, so this would be something like:

private static final int DEFAULT_MERGE_FACTOR =
 
Integer.parseInt(System.getProperty("org.apache.lucene.mergeFactor","10"));

In IndexWriter.java.

What other candidates are there for this treatment?

Doug

---------------------------------------------------------------------
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


Mime
View raw message