lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Holliday (JIRA)" <>
Subject [jira] Commented: (LUCENE-674) Error in FSDirectory if incorrectly specified
Date Wed, 20 Sep 2006 22:43:24 GMT
    [ ] 
Ryan Holliday commented on LUCENE-674:

I'm not sure if "the user specified the wrong directory" is necessarily the correct situation
here.  Unless a user specifically sets the org.apache.lucene.lockDir property, they aren't
really choosing the lock directory location - Lucene uses the property as a
default, without any input from the user.  A user who runs into this problem will see only
something like "Cannot create directory: /temp" in their logs, and then has to go through
the source code to figure out why anything is trying to create that directory.

The code already defaults to using the index directory for lock files (which the user DID
specify) if the org.apache.lucene.lockDir property and the properties are not
set - it doesn't seem like much of a stretch to just modify the code to also use the index
directory if at least the property is invalid.

> Error in FSDirectory if incorrectly specified
> ------------------------------------------------------------
>                 Key: LUCENE-674
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 2.0.0
>         Environment: Reported on a Linux system under Tomcat
>            Reporter: Ryan Holliday
> A user of the JAMWiki project ( reported an error with the following
stack trace:
> SEVERE: Unable to create search instance /usr/share/tomcat5/webapps/jamwiki-0.3.4-beta7/test/base/search/indexen
> Cannot create directory: /temp
>         at
>         at
>         at
>         at
> The culprit is that the property was incorrectly specified on the user's
system.  Lucene could easily handle this issue by modifying the FSDirectory.init() method.
 Currently the code uses the index directory if and org.apache.lucene.lockDir
are unspecified, but it could use that directory if those values are unspecified OR if they
are invalid.  Doing so would make Lucene a bit more robust without breaking any existing installations.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message