Thanks for closing this off. it'd have been a pretty serious thing if soft commits weren't working.
Erick On Wed, Nov 26, 2014 at 12:58 PM, Andreas Hubold <andreas.hub...@coremedia.com> wrote: > Thank you, Shawn and Erick! > > With your hint about the re-used searcher I was able to find my error. I > must wait for the newly opened searcher when calling the commit method: > > solrServer.commit(false, true /*waitSearcher*/, true /*softCommit*/); > > instead of > > solrServer.commit(false, false, true); > > Thanks, > Andreas > > > Erick Erickson wrote on 11/26/2014 05:35 PM: >> >> As Shawn says, deletes should be >> visible after a soft commit. >> >> Let's see the code though. If you re-use a searcher that >> you had open before the commit, it'll still see the old >> snapshot of the index including the deleted documents. >> Or if you do open a new searcher and any autowarming >> hasn't completed you'll still see the snapshot before the commit. >> >> Best, >> Erick >> >> On Wed, Nov 26, 2014 at 8:16 AM, Shawn Heisey <apa...@elyograg.org> wrote: >>> >>> On 11/26/2014 8:18 AM, Andreas Hubold wrote: >>>> >>>> But I'm still not totally sure. Does a soft commit also make deleted >>>> documents invisible? >>>> >>>> In a test with an EmbeddedSolrServer I triggered a soft commit and was >>>> still able to find a deleted document afterwards. Is this as expected? >>> >>> All changes to the index, including deletes, are not seen by clients >>> until a commit with openSearcher=true is done. A soft commit *should* >>> cause the deletes to take effect, along with any adds or updates done >>> since the last searcher was opened. >>> >>> There's a problem somewhere if that's not happening, either in your >>> indexing code or Solr. >>> >>> Thanks, >>> Shawn >>> >> . >> > >
