That explains true, but what about false? Why would I ever set it to
false? I f I don't wait, how will I ever know when the new searcher
is ready?
On Nov 18, 2008, at 10:27 PM, Ryan McKinley wrote:
waitFlush I'm not sure...
waitSearcher=true it will wait until a new searcher is opened after
your commit, that way the client is guaranteed to have the results
that were just sent in the index. if waitSearcher=true, a query
could hit a searcher that does not have the new documents in the
index.
On Nov 18, 2008, at 9:13 PM, Grant Ingersoll wrote:
Was wondering if anyone can fill me in on the when and why I would
set waitFlush and waitSearcher to false when sending a commit
command? I think I understand what they do technically (I've
looked at the code), but I am not clear about why I would want to
do it. Is there a risk in setting them to false? Wouldn't my
response return a lot faster if it was set to false? Yet, the
default is true for both, so I assume there is a reason I want to
wait...
Thanks,
Grant
