On Wed, Jul 18, 2012 at 6:59 PM, Chris Hostetter <[email protected]>wrote:
> > : I trying to split the query into multiple subqueries > : (LocalSolrQueryRequest) in my custom handler and call SearchHandler's > : handleRequestBody on each of these LocalSolrQueryRequests. Its sort of a > > FWIW: I'm not totally understanding what you are trying to do, but > generally speaking it is extremely rare that a piece of code should ever > call core.getSearcher(). > Yes I agree. I was just trying to get a hold of the various classes. > If you want to "fork" a request and process it in paralel -- or process > multiple variations of it -- i would not suggest making your own > LocalSolrQueryRequest objects, because each one could potentially have a > differnet SolrIndexSearcher if a newSearcher event takes place in between > instantiating your LocalSolrQueryRequest. I would either consistently reuse the original SolrQueryRequest in all of > your sub-requests, or write your own SolrQueryRequest subclass that always > reuses the SolrIndexSearcher from your "root" request. > Yeah, in that case each of them could have different version of the index. I think if I use LocalSolrQueryRequests, because of the possibility of having different SolrIndexSearchers, there could also be searcher leak as I might open one and by the time the time I close the old one, I could have a new searcher in the place of old one. Am i right? > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
