bq: does that preclude us from doing what we're trying to do above? Not at all. You just have to process each response and combine them perhaps.
In this case, you might be able to get away with just specifying the shards parameter to the query and having the app layer deal with the responses. At least that's what I'd start with, keeping in mind that more complex processing may be necessary eventually. Best, Erick On Wed, Jul 15, 2015 at 10:00 AM, Chetan Vora <chetanv...@gmail.com> wrote: > Mikhail > > We do add new nodes with our custom results in some cases... just curious- > does that preclude us from doing what we're trying to do above? FWIW, we > can avoid the custom nodes if we had to. > > Chetan > > On Wed, Jul 15, 2015 at 12:39 PM, Mikhail Khludnev < > mkhlud...@griddynamics.com> wrote: > >> >> >> On Wed, Jul 15, 2015 at 10:46 AM, Chetan Vora <chetanv...@gmail.com> >> wrote: >> >>> Hi all >>> >>> I asked a related question before but couldn't get any response (see >>> SolrQueryRequest in SolrCloud vs Standalone Solr), asking it differently >>> here. >>> >>> Is there a way to invoke >>> >>> IndexSearcher.search(Query, Collector) over a SolrCloud collection so that >>> in invokes the search/collect implicitly on individual shards of the >>> collection? If not, how does one do this explicitly? >>> >>> I have a usecase that was implemented using custom request handler in >>> standalone Solr and we're trying to move to SolrCloud. >> >> >> In your custom request handler do you add any new "nodes" into response? >> or you just modifies the standard response structure? >> >> It is necessary for >>> us to understand how to do the above so we can use SolrCloud >>> functionality. >>> >>> Thanks and would *really really* appreciate ANY help. >>> >>> Regards >>> CV >>> >> >> >> >> -- >> Sincerely yours >> Mikhail Khludnev >> Principal Engineer, >> Grid Dynamics >> >> <http://www.griddynamics.com> >> <mkhlud...@griddynamics.com> >>
