Re: Retain the index

Now it looks like you are creating the IndexWriter with create=false when in fact there is no existing index in that directory. Mike <[EMAIL PROTECTED]> wrote: > I got this error after dleteing that file > > Exception in thread "main" java.io.FileNotFoundException: > C:\pIndexed\segments (The s

Re: Retain the index

I got this error after dleteing that file Exception in thread "main" java.io.FileNotFoundException: C:\pIndexed\segments (The system cannot find the file specified) at java.io.RandomAccessFile.open(Native Method) at java.io.RandomAccessFile.(RandomAccessFile.java:212) at or

Re: Retain the index

You could create your own SimpleFSLockFactory, specifying a different lock dir, and pass that to FSDirectory.getDirectory. This way you can control where the lock file is created and hopefully put it in a dir that you're able to delete from. Or, update to a newer version of Lucene, which

Re: Retain the index

hey i am running my indexer on application server/ production server.. i cant delete the files.. please give me a good solution.. changing true and false is not working..if have add new docs.. can nay one help me..please... regards anjana On Jan 31, 2008 3:02 PM, Michael McCandless <[EMAIL PROT

Re: Retain the index

Physically delete the file, or, use IndexReader.unlock static method. Mike On Jan 31, 2008, at 4:26 AM, anjana m wrote: How do i remove the locks..? On Jan 31, 2008 2:49 PM, Michael McCandless <[EMAIL PROTECTED]> wrote: It looks like you are passing "true" to FSDirectory.getDirectory

Re: Retain the index

How do i remove the locks..? On Jan 31, 2008 2:49 PM, Michael McCandless <[EMAIL PROTECTED]> wrote: > > It looks like you are passing "true" to FSDirectory.getDirectory, > which you shouldn't do. Always pass "false" to that. (Newer > versions of Lucene have deprecated the create flag to FSDir

Re: Retain the index

On false.. i get this error... wht do you suggest me to do further i am using lucene 1.4 final.. plsease help Exception in thread "main" java.io.IOException: Lock obtain timed out: [EMAIL PROTECTED]:\DOCUME~1\ANJANA\LOCALS~1\Temp\lucene- 26fee40bb91b3504c3589207f2d7efa3-write.lock at o

Re: Retain the index

It looks like you are passing "true" to FSDirectory.getDirectory, which you shouldn't do. Always pass "false" to that. (Newer versions of Lucene have deprecated the create flag to FSDirectory, leaving it entirely to IndexWriter). On the lock obtain timed out, probably that's a left over

Re: Retain the index

with true: i finding a serious problem when i need new index please help.. but how can ikeep chnaging the true flase option.. :( please help me...:( Exception in thread "main" java.io.IOException: Cannot delete _17.cfs at org.apache.lucene.store.FSDirectory.create(FSDirectory.java:144)

Re: Retain the index

Set the parameter to false as per the documentation Erick On Jan 27, 2008 5:11 AM, anjana m <[EMAIL PROTECTED]> wrote: > yes i dont want the old index to be deletd since its running on my app > server.. > any suggestion..? > > On Jan 27, 2008 3:07 PM, Daniel Naber <[EMAIL PROTECTED]> > wrote

Re: Retain the index

yes i dont want the old index to be deletd since its running on my app server.. any suggestion..? On Jan 27, 2008 3:07 PM, Daniel Naber <[EMAIL PROTECTED]> wrote: > On Sonntag, 27. Januar 2008, anjana m wrote: > > > IndexWriter writer = new IndexWriter(indexDir, new > > StandardAnalyzer()

Re: Retain the index

On Sonntag, 27. Januar 2008, anjana m wrote: >         IndexWriter writer = new IndexWriter(indexDir, new > StandardAnalyzer(), true); The true parameter means that the old index will be deleted, is that your problem? Regards Daniel -- http://www.danielnaber.de -

Re: Retain the index

My Indexing Code --- public void index(File indexDir, File dataDir) throws IOException { if (!dataDir.exists() || !dataDir.isDirectory()) { throw new IOException(dataDir + " does not exist or is not a directory"); } IndexWrite

Re: Retain the index

Check if there are any lock files in your index directory after the process is completed. There should be no lock files if the index was correctly closed . On Jan 25, 2008 8:59 AM, Erick Erickson <[EMAIL PROTECTED]> wrote: > This should not be happening. I've got to assume that you have > more t

Re: Retain the index

This should not be happening. I've got to assume that you have more than one IndexWriter open at the same time. There's no problem at all with updating an existing index that I've ever seen, any similar errors on my part have been coding errors on my part. So first make absolutely sure that your

Retain the index

I want to retain the older index. I dont want to delete the older index. Please help me. Does the recent release has the option to update the indexes without deleting it. I am ruuning the indexer on my sun application server. and its thorwing exceptions like cannot delete indexex. now every time