[ http://issues.apache.org/jira/browse/LUCENE-674?page=comments#action_12436384 ] 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 java.io.tmpdir 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 java.io.tmpdir 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 java.io.tmpdir property is invalid. > Error in FSDirectory if java.io.tmpdir incorrectly specified > ------------------------------------------------------------ > > Key: LUCENE-674 > URL: http://issues.apache.org/jira/browse/LUCENE-674 > 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 (http://jamwiki.org/) 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 > java.io.IOException: Cannot create directory: /temp > at org.apache.lucene.store.FSDirectory.init(FSDirectory.java:171) > at > org.apache.lucene.store.FSDirectory.getDirectory(FSDirectory.java:141) > at > org.apache.lucene.store.FSDirectory.getDirectory(FSDirectory.java:117) > at > org.jamwiki.search.LuceneSearchEngine.getSearchIndexPath(LuceneSearchEngine.java:318) > The culprit is that the java.io.tmpdir 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 > java.io.tmpdir 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
