well just checked the api, the deleteDocuments(term[]) method deletes any document containing any of the terms.
I think I will go to the trunk version. best. -c.a. On Sat, Aug 2, 2008 at 12:14 AM, Cam Bazz <[EMAIL PROTECTED]> wrote: > > from what I understand: > there is a deleteDocuments by a term array method? > > > I was asking if there was a side effect of deleting from indexReader that i > get from an indexsearcher and not the writer. > > Best. > > > On Sun, Jul 27, 2008 at 9:44 PM, Karsten F. <[EMAIL PROTECTED] > > wrote: > >> >> Hi, >> >> only to be sure: >> You know IndexModifier.deleteDocument(int)? >> It is deprecated, because you should use >> IndexWriter.deleteDocuments(Term[]). >> >> What do you mean with "index is committed". >> If you mean "optimize()" the document number will change (so there is a >> side-effect;-) >> >> best regards >> Karsten >> >> >> cambazz wrote: >> > >> > hello, >> > >> > the thing is: >> > >> > I got a indexwriter and indexsearcher. >> > >> > I do a indexsearcher.getIndexReader.delete(int id) >> > >> > would not that cause problems? there is not a way to delete from >> > indexwriter, and I think i will cause a lock issue deleting from >> > indexsearcher. >> > >> > best, >> > -C.B. >> > >> -- >> View this message in context: >> http://www.nabble.com/deleting-documents-with-doc-id-tp18619372p18679168.html >> Sent from the Lucene - Java Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >
