Re: Query on searchAfter API usage in IndexSearcher

I have encountered the same problem, I wonder if anyone know the solution? Regards, Jacky -- Sent from: http://lucene.472066.n3.nabble.com/Lucene-Java-Users-f532864.html - To unsubscribe, e-mail: java-user-unsubscr

Re: lock file of lucene

hi, yes, but there maybe several programs to write the index. If a program is writing into the index, the index database maybe corrupted when another program unlocks it Best Regards. jacky - Original Message - From: "Bhavin Pandya" <[EMAIL PROTECTE

lock file of lucene

that? Best Regards. jacky

Re: duplicate fields

hi Daniel, How do you use a separate database to check the duplicate fields? It is interesting! Best Regards. jacky - Original Message - From: "Daniel Noll" <[EMAIL PROTECTED]> To: Sent: Friday, September 08, 2006 3:08 PM Subject: Re:

delete operation

t know how lucene did this. So when the lucene database is updated, how to notify to reopen the IndexSearcher since there may be several applications to search this lucene database? Best Regards. jacky

Re: parameter create in IndexWriter

I see, thanks, Erick! I will change some architecture of our application because an IndexWriter will be kept open when program is running. Best Regards. jacky - Original Message - From: "Erick Erickson" <[EMAIL PROTECTED]> To: Sent: Thursday, Se

Re: parameter create in IndexWriter

I am afraid i don't understand it. Input the wrong path? This will be happen rarely since the index path is always hard code in the config file. And usually, users need to create a brand new index, and then append the new document into it. Best Regards.

parameter create in IndexWriter

wise. I know we can do this in the application, but it is complex sometimes. Best Regards. jacky

Re: Keep hits in results

Oh, that is not a good news. So when the index is updated, the held searcher will get the old documents? That is indeed not a good idea to keep the hits. I had thought lucene did this work for users. Best Regards. jacky - Original Message - From: "Erik Ha

Re: Keep hits in results

Erik, thanks! You are right! It is not a good idea to hold on a hits since the index will be updated. So, when i keep a hits, and then the index is updated, the searcher will be auto-updated,too. rigtht? Best Regards. jacky - Original Message - From: "

Re: Keep hits in results

. So,that will not cost much memory and you can get the results whenever you want, and the performance will be better, right? (Don't think about state of users in webapp for a while) Best Regards. jacky - Original Message - From: "Doron Cohen" <[EM

Keep hits in results

ginal Hits which will not waste much memory. Best Regards. jacky

Re: IndexSearcher executed concurrently

ROTECTED]> wrote: On Tue, 2006-09-05 at 17:57 +0800, jacky wrote: > 1. I wander if concurrent users can get the right results with > different queries since the class has only one IndexSearcher instance. > > 2. As we know, a new IndexSearcher can be created when user request >

IndexSearcher executed concurrently

Thanks for you help! Best Regards. jacky