Re: neither IndexWriter nor IndexReader would delete documents

2007-11-20 Thread Daniel Naber
On Montag, 19. November 2007, flateric wrote: > the number returned by delete is 0, but the "uid" shows up in Luke so it > is there. Not sure what the problem might be, but it can surely be analyzed if you write a small self-contained test-case and post it here. Regards Daniel -- http://www.

Re: neither IndexWriter nor IndexReader would delete documents

2007-11-19 Thread flateric
Hallo Daniel; the number returned by delete is 0, but the "uid" shows up in Luke so it is there. I close the reader after every delete and then re-open it for the next delete (see my code snippets below). Eric Daniel Naber-10 wrote: > > On Sonntag, 18. November 2007, flateric wrote: > >> Ind

Re: neither IndexWriter nor IndexReader would delete documents

2007-11-19 Thread Erick Erickson
Also, are you re-opening the reader underlying your *searcher* before you query and still get the deleted docs? Also, look with Luke to see if the specific uid you *think* you've deleted is really gone. Best Erick On Nov 19, 2007 6:42 AM, Daniel Naber <[EMAIL PROTECTED]> wrote: > On Sonntag, 18

Re: neither IndexWriter nor IndexReader would delete documents

2007-11-19 Thread Daniel Naber
On Sonntag, 18. November 2007, flateric wrote: > IndexReader ir = IndexReader.open(fsDir); > ir.deleteDocuments(new Term("uid", uid)); > ir.close(); > > Has absolutely no effect. What number does ir.deleteDocuments return? If it's 0, the uid cannot be found. If it's > 0: note that you need to re

Re: neither IndexWriter nor IndexReader would delete documents

2007-11-19 Thread flateric
Hallo Daniel; thank you for your quick reply. The "uid" field exists (UN_TOKENIZED and stored). The IndexWriter is also closed while I'm using the IndexReader to delete. Thanks, Eric Daniel Naber-10 wrote: > > On Sonntag, 18. November 2007, flateric wrote: > >> Has absolutely no effect. I al

RE: neither IndexWriter nor IndexReader would delete documents

2007-11-19 Thread flateric
Hallo Kapil; thanks for your quick answer: * "An IndexReader can be opened on a directory for which an IndexWriter is opened already, but it cannot be used to delete documents from the index then. " sounded like a match, but I checked that and the IndexWriter is definitely closed. Regards, Eric

RE: neither IndexWriter nor IndexReader would delete documents

2007-11-18 Thread Chhabra, Kapil
Hi, Checkout for the following lines in the documentation of IndexReader: * "An IndexReader can be opened on a directory for which an IndexWriter is opened already, but it cannot be used to delete documents from the index then. " * "Once a document is deleted it will not appear in TermDocs or Term

Re: neither IndexWriter nor IndexReader would delete documents

2007-11-18 Thread Daniel Naber
On Sonntag, 18. November 2007, flateric wrote: > Has absolutely no effect. I also tried delete on the IndexWriter - no > effect. Please use the tool Luke to have a look inside your index to see if a document with field "uid" and the uid you're expecting really exists. The field should be UN_TOK