firstSearcher and newSearcher events

[Grant Ingersoll <gs...@apache.org>]

Is there a way, in a request, to know if the query being sent is from  
a firstSearcher event?  For instance, I've noticed that if one has the  
shards parameter in the firstSearcher call (I was just trying out some  
distributed stuff) it hangs Solr.

Presumably, we'd have to add a parameter to the request, right?  Just  
wasn't sure if there was some other low level setting that one could  
check.

Thanks,
Grant

Re: firstSearcher and newSearcher events

[Grant Ingersoll <gs...@apache.org>]

https://issues.apache.org/jira/browse/SOLR-1237

On Jun 22, 2009, at 6:48 PM, Yonik Seeley wrote:

> On Mon, Jun 22, 2009 at 5:05 PM, Grant  
> Ingersoll<gs...@apache.org> wrote:
>> I think I'm just going to add a parameter for those events that get  
>> passed
>> along by those calls.  Currently, those events will hang if the  
>> request has
>> &shards= passed in.
>
> Good point - it does seem like request handlers should be able to tell
> if the request is for the purposes of warming or not.
>
> -Yonik
> http://www.lucidimagination.com

Re: firstSearcher and newSearcher events

[Yonik Seeley <yo...@lucidimagination.com>]

On Mon, Jun 22, 2009 at 5:05 PM, Grant Ingersoll<gs...@apache.org> wrote:
> I think I'm just going to add a parameter for those events that get passed
> along by those calls.  Currently, those events will hang if the request has
> &shards= passed in.

Good point - it does seem like request handlers should be able to tell
if the request is for the purposes of warming or not.

-Yonik
http://www.lucidimagination.com

Re: firstSearcher and newSearcher events

[Grant Ingersoll <gs...@apache.org>]

On Jun 22, 2009, at 4:41 PM, Chris Hostetter wrote:

>
> : Date: Mon, 8 Jun 2009 10:48:05 -0400
> : From: Grant Ingersoll
> : Subject: firstSearcher and newSearcher events
> :
> : Is there a way, in a request, to know if the query being sent is  
> from a
> : firstSearcher event?  For instance, I've noticed that if one has  
> the shards
>
> I don't think so ... the listeners just fire off hte requests using  
> the
> standard APIs.
>
> you might be able to do something clever to "guess" that you are in a
> firstSearcher or newSearcher event (i'm thinking about stuff like  
> trying
> to fetch a searcher directly from the core and then comparing it to  
> hte
> searcher in the request) but i wouldn't rely on it.
>


I think I'm just going to add a parameter for those events that get  
passed along by those calls.  Currently, those events will hang if the  
request has &shards= passed in.

-Grant

Re: firstSearcher and newSearcher events

[Chris Hostetter <ho...@fucit.org>]

: Date: Mon, 8 Jun 2009 10:48:05 -0400
: From: Grant Ingersoll
: Subject: firstSearcher and newSearcher events
: 
: Is there a way, in a request, to know if the query being sent is from a
: firstSearcher event?  For instance, I've noticed that if one has the shards

I don't think so ... the listeners just fire off hte requests using the 
standard APIs.

you might be able to do something clever to "guess" that you are in a 
firstSearcher or newSearcher event (i'm thinking about stuff like trying 
to fetch a searcher directly from the core and then comparing it to hte 
searcher in the request) but i wouldn't rely on it.




-Hoss