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
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 o
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);
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 complete
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 change
Hi,
I've read about soft commits in Erick Erickson's excellent blog article [1]:
> The thing to understand most about soft commits are that they will
make documents visible
But I'm still not totally sure. Does a soft commit also make deleted
documents invisible?
In a test with an EmbeddedS
