Re: Lucene Question about Query

I used SnowBall Analyzer with English language.In snowball analyzer is it possible? On Mon, May 7, 2012 at 9:48 AM, Li Li wrote: > what's your analyzer? > if you use standard analyzer, I think this won't happen. > if you want to get exact match of name field, you should index this > field but

Re: IndexWriter.isLock()

So if my program interrupts, the lock files in the indexes will be released in the next run. hoom? That's so good. Thank you Mr.McCandless for your help. On Mon, May 7, 2012 at 5:04 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > On Mon, May 7, 2012 at 7:19 AM, S Eslamian wrote: >

Many keywords problem

Hi, I met a problem about how to search many keywords in about 5,000,000 documents.For example the query may be like "(a1 or a2 or a3 a200) and (b1 or b2 or b3 or b4 . b400)",I found it will take vey long time(40seconds) to get the the answer in only one field(Title field),and JV

Re: pruning package- pruneAllPositions

Hi Zeynep, I was facing the same issue in CarmelUniformTermPruningPolicy in package org.apache.lucene.index.pruning . I think the issue is in the while loop condition in following peice of code *while ((docsPos < (docs.length - 1))* * && termPositions.doc() > docs[docsPos].doc) {* * docsPos++;*

Re: Measuring precision and recall in lucene to compare two sets of results

Hi, You can use kendall's tau. An article titled Comparing top k lists by Ronald Fagin, Ravi Kumar and D. Sivakumar explaines different methods. Best Regards, ZP -- View this message in context: http://lucene.472066.n3.nabble.com/Measuring-precision-and-recall-in-lucene-to-compare-two-sets-

Re: pruning package- pruneAllPositions

Thanks for the link. I reviewed it. Here are more details about the exception: I used contrib/benchmark/conf/wikipedia.alg to index wikipedia dump with MAddDocs: 20. I wanted to index only a specific period of time so I added an if statement in doLogic of AddDocTask class. I tried to prune t

Re: IndexWriter.isLock()

On Mon, May 7, 2012 at 7:19 AM, S Eslamian wrote: > hmm... , What is a leftover lock file? > > You know I debug my code, befor index folder has lock file, till line 7. > Then I close the program, like in a real run an interrupt has happened. How do you close it? Just kill the process? That is w

Re: IndexWriter.isLock()

Thanks a lot. You mean this happens because of the NIOFSDirectory which I'm using. Am I right? But why the lock releases after calling isLock() method? I check the index folder before this call and it has write.lock yet. On Mon, May 7, 2012 at 3:58 PM, Shai Erera wrote: > If I understand correc

Re: IndexWriter.isLock()

If I understand correctly, you're using the NativeFSLockFactory and that's the expected behavior -- unlike SimpleFSLockFactory, if you terminate the JVM and then restart the program, the lock is not held anymore -- that's the advantage of using native-fs-lock because nobody really holds the lock an

Re: IndexWriter.isLock()

hmm... , What is a leftover lock file? You know I debug my code, befor index folder has lock file, till line 7. Then I close the program, like in a real run an interrupt has happened. Next I debug the program again with that index folder which has the lock file and it shouldn't passes the if claus

Re: IndexWriter.isLock()

My guess is you had a leftover lock file. With NativeFSLockFactory (used by NIOFSDirectory), the presence of a lock file does not mean the lock is held (unlike the older SimpleFSLockFactory). The code that checks if the lock is held simply acquires and then releases the lock. So if you had a lef