good.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wait-Flush-Wait-Searcher-and-commit-Scenarios-tp491509p4131651.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Tue, Nov 18, 2008 at 10:55 PM, Mark Miller <[EMAIL PROTECTED]> wrote:
> Does waitFlush do anything now? I only see it being set if eclipse is not
> missing a reference...
Not currently. The idea was that if waitFlush== false that the call
would be totally asynchronous and return immediately.
I am using waitSearcher=false with a crawler. The crawling thread
finishes a set of stuff, and calls . It does not want to
search, it gets back to crawling ASAP
On Nov 18, 2008, at 11:35 PM, Grant Ingersoll wrote:
That explains true, but what about false? Why would I ever set it
to fal
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 a
Does waitFlush do anything now? I only see it being set if eclipse is
not missing a reference...
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 ju
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
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
