lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26196] - IndexWriter problem when create set to false
Date Thu, 04 Mar 2004 14:43:01 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26196>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26196

IndexWriter problem when create set to false





------- Additional Comments From nick.west@intercea.co.uk  2004-03-04 14:43 -------
Sorry, mabybe I'm not making myself clear.

If I have a directory "C:\\indexes" and have configured this to contain my 
index files, then I'd expect the constructor to create the files there if not 
already in existance, or at least an option to enforce this.  I would hope 
that in the initial setup the same constructor would be used as that for 
future constructions.
I agree that if the directory does not exist, then yes a FileNotFoundException 
should be thrown, but as it's the actual index files I don't see the problem 
with automating the creation.  If there is a logical reason for throwing this 
exception, then I'll be happy, if not, then I see the most logical answer to 
create the files Lucene needs to unless the actual directory is wrong.

Does that kind of make any more sense?

---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org


Mime
View raw message