Re: Unexpected returning false from IndexWriter.tryDeleteDocument

2014-01-13 Thread Derek Lewis
McCandless < luc...@mikemccandless.com> wrote: > On Thu, Jan 2, 2014 at 7:53 PM, Derek Lewis wrote: > > Sorry for the delay responding. Holidays and all that. :) > > No problem. > > > The retry approach did work, our process finished in the end. At some > > p

Re: Unexpected returning false from IndexWriter.tryDeleteDocument

2014-01-02 Thread Derek Lewis
lterIndexReader with addIndices. That sounds very promising. I'm going to investigate doing our duplicate filtering that way instead. Thanks again for the help. Cheers :) Derek Lewis On Sat, Dec 21, 2013 at 5:13 AM, Michael McCandless < luc...@mikemccandless.com> wrote: > OK I see; so

Re: Unexpected returning false from IndexWriter.tryDeleteDocument

2013-12-20 Thread Derek Lewis
s an "error" (it sounds like > it throws an exception and retries again later until it succeeds)... > it's better to delete those documents "the old fashioned way". > Relying on when IW starts/finishes merges is fragile (it's an > implementation

Re: Unexpected returning false from IndexWriter.tryDeleteDocument

2013-12-20 Thread Derek Lewis
ttp://blog.mikemccandless.com > > > On Fri, Dec 20, 2013 at 12:12 PM, Derek Lewis wrote: > > Hello, > > > > I have a problem where IndexWriter.tryDeleteDocument is returning false > > unexpectedly. Unfortunately, it's in production, on indexes that have > >

Unexpected returning false from IndexWriter.tryDeleteDocument

2013-12-20 Thread Derek Lewis
Hello, I have a problem where IndexWriter.tryDeleteDocument is returning false unexpectedly. Unfortunately, it's in production, on indexes that have since been merged and shunted around all over, and I've been unable to create a scenario that duplicates the problem in any development environments