How to view deleted documents and undelete(int docID)

Hi, I am wondering whether this is possible at all Regarding SegmentReader.document(n,..), an exception is thrown if (isDeleted(n) == true). So I cannot get a hold of document n if it is deleted. Despite that, is there a way to view the deleted document and undelete a single document?

Obtain Lock file timeout during deleteDocument()

Hi, I am a little confused, probably, because I missed some detail when looking through the code of lucene 2.1. Scenario: Deleting documents works for a while, eventually, I get the exception that obtaining the lock files has timed out. I was trying to find an answer to this. I call

Re: Obtain Lock file timeout during deleteDocument()

On Wednesday 30 May 2007 11:49:41 Michael McCandless wrote: Martin Kobele [EMAIL PROTECTED] wrote: I was trying to find an answer to this. I call IndexReader.deleteDocument() for the _first_ time. If my index has several segments, my IndexReader is actually a MultiReader. Therefore

Re: Obtain Lock file timeout during deleteDocument()

On Wednesday 30 May 2007 11:53:09 Martin Kobele wrote: On Wednesday 30 May 2007 11:49:41 Michael McCandless wrote: You are only using a single instance of IndexReader, right? If for example you try to make a new instance of IndexReader and then call deleteDocument on that new one, then you

phrases containing escaped quotes

Hi, I tried to parse the following phrase: foo \bar\ I get the following exception: org.apache.lucene.queryParser.ParseException: Lexical error at line 1, column 18. Encountered: EOF after : \) Am I mistaken that foo \bar\ is a valid phrase? Thanks! Martin pgp6qEn6ntvUi.pgp Description:

Re: phrases containing escaped quotes

thank you! I was indeed using lucene 2.0 and it works very nicely with 2.1 thanks! Martin On Tuesday 15 May 2007 09:59:42 Michael Busch wrote: Martin Kobele wrote: Hi, I tried to parse the following phrase: foo \bar\ I get the following exception

How to warm up

Hi, I have read it several times that sometimes it is practical to warm up a searcher. What exactly does that mean? Would I simply perform a search for foo bar or something like that? What happens inside the searcher so that it becomes 'warmed up'? Thank you! Regards, Martin

many many boolean queries

Hi, since I use many wildcards, I get the exception, that the number of boolean queries exceeds the default value (1024). I could simply increase the value to like 10,000 or something What would be the trade-off of using a high max value? Thanks! Martin

Some documents are not added to the index

Hi, several threads add document to the same index. As noted in the FAQ, adding documents is thread safe. (I even synchronize my static index writer when I add documents. just to make sure.) However, after addind all my documents, the index does not contain all of the documents. When I run it

Re: Some documents are not added to the index

On Wednesday 17 May 2006 12:03, Yonik Seeley wrote: On 5/17/06, Martin Kobele [EMAIL PROTECTED] wrote: several threads add document to the same index. As noted in the FAQ, adding documents is thread safe. (I even synchronize my static index writer when I add documents. just to make sure

Re: Some documents are not added to the index

On Wednesday 17 May 2006 09:55, karl wettin wrote: I can only guess out of the blue. Do you clear the index now and then when creating a new IndexWriter? You say there is only one instance of that so that would not be it then. how do I clear the index? I create an IndexWriter with the create

is writing in an index thread safe?

Hi, is writing into an index with several threads safe? I have a static IndexWriter and all the threads use that one to do an addDocument(Document). Thanks! Martin -- Martin Kobele Software Engineer - To unsubscribe, e-mail

Re: is writing in an index thread safe?

ouch, I missed it there. I always thought that the FAQ is really good! thank you! sorry for the noise. Martin On Friday 05 May 2006 16:04, Otis Gospodnetic wrote: Yes, and I believe it's in the FAQ. Otis - Original Message From: Martin Kobele [EMAIL PROTECTED] To: java-user

Re: using search instead of explain

- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Martin Kobele Software Engineer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e

Re: using search instead of explain

, Martin Kobele [EMAIL PROTECTED] wrote: thank you very much. Let's hope the developers can get this bug fixed soon :) While it would be nice to have a 100% accurate explain(), it should only be used for debugging purposes (and it's normally going to be *much* slower than using a HitCollector

using search instead of explain

-zero. Is there any relation between the value of the explanation and the score? Thanks! Regards, Martin Kobele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]