Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@www.apache.org Received: (qmail 97377 invoked from network); 18 Mar 2004 19:42:21 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 18 Mar 2004 19:42:21 -0000 Received: (qmail 6200 invoked by uid 500); 18 Mar 2004 19:41:49 -0000 Delivered-To: apmail-jakarta-lucene-dev-archive@jakarta.apache.org Received: (qmail 6178 invoked by uid 500); 18 Mar 2004 19:41:49 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 6136 invoked from network); 18 Mar 2004 19:41:48 -0000 Received: from unknown (HELO web12708.mail.yahoo.com) (216.136.173.245) by daedalus.apache.org with SMTP; 18 Mar 2004 19:41:48 -0000 Message-ID: <20040318194151.10940.qmail@web12708.mail.yahoo.com> Received: from [194.152.226.172] by web12708.mail.yahoo.com via HTTP; Thu, 18 Mar 2004 11:41:51 PST Date: Thu, 18 Mar 2004 11:41:51 -0800 (PST) From: Otis Gospodnetic Subject: Re: cvs commit: jakarta-lucene/src/java/org/apache/lucene/store Lock.java To: Lucene Developers List In-Reply-To: <4059F89F.3030403@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I actually already documented these properties in xdocs format (commit coming). But making things public and using Javadocs is also a good idea. LOCK_DIR - good catch - changed things. Otis --- Doug Cutting wrote: > otis@apache.org wrote: > > - Added support for setting various Lucene properties via system > properties. > > Otis, > > Thanks for doing this. > > Now we need to get these properties into the documentation. The > easiest > approach is simply to make all of these 'private static final' fields > > into 'public static final' fields which then mention the system > property > which can be used to override their default. > > Also, is Lock.LOCK_DIR actually used? The diff didn't show that. > Since > this is to be used by FSDirectory, the parameter should probably be > in > FSDirectory.java, not Lock.java. It wouldn't be relevant to, e.g., a > > database-based lock implementation. > > And when it is used we should permit it to be relative to the index > directory. So, in FSDirectory, we might have a field like: > > private File lockDir; > > and in FSDirectory ctor, add something like: > > lockDir = new File(LOCK_DIR); > if (!lockDir.isAbsolute()) { > lockDir = new File(directory, LOCK_DIR); > } > > Then use lockDir when creating lock file names. This will permit > someone to simply set org.apache.lucene.lockdir to "." to get the old > > behaviour where lock files are placed alongside indexes. > > Does that makes sense? > > Doug > > --------------------------------------------------------------------- > To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: lucene-dev-help@jakarta.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-dev-help@jakarta.apache.org