Thanks Chris. This help.
Regards, Rohan On Mon, Oct 22, 2018 at 12:26 PM Chris Ulicny <culicny@iq.media> wrote: > There weren't any particular problems we ran into since the client that > makes the queries to multiple collections previously would query multiple > cores using the 'shards' parameter before we moved to solrcloud. We didn't > have any complicated sorting or scoring requirements fortunately. > > The one thing I remember looking into was what solr would do when two > documents with the same id were found in both collections. I believe it > just non-deterministically picked one, probably the one that came in first > or last. > > Depending on how many collections you need to query simultaneously, it's > worth looking into using aliases for lists of collections as Alex > mentioned. > > Unfortunately, in our use case, it wasn't worth the headache of managing > aliases for every possible combination of collections that needed to be > queried, but we would have preferred to use aliases. > > On Mon, Oct 22, 2018 at 2:27 PM Rohan Kasat <rohan.ka...@gmail.com> wrote: > > > Thanks Alex. > > I check aliases but dint focused much , will try to relate more to my use > > case and have a look again at the same. > > I guess the specification of collection in the query should be useful. > > > > Regards, > > Rohan Kasat > > > > On Mon, Oct 22, 2018 at 11:21 AM Alexandre Rafalovitch < > arafa...@gmail.com > > > > > wrote: > > > > > Have you tried using aliases: > > > > > > > > > http://lucene.apache.org/solr/guide/7_5/collections-api.html#collections-api > > > > > > You can also - I think - specify a collection of shards/collections > > > directly in the query, but there may be side edge-cases with that (not > > > sure). > > > > > > Regards, > > > Alex. > > > On Mon, 22 Oct 2018 at 13:49, Rohan Kasat <rohan.ka...@gmail.com> > wrote: > > > > > > > > Hi All , > > > > > > > > I have a SolrCloud setup with multiple collections. > > > > I have created say - two collections here as the data source for the > > > both > > > > collections are different and hence wanted to store them differently. > > > > There is a use case , where i need to query both the collections and > > show > > > > unified search results. > > > > The fields in the schema are same. ( say - title , description , > date ) > > > > Is there any specific way i can do this directly with the collections > > API > > > > or something like that? > > > > Or i need to write a federator and combine results from search to the > > > > respective collections and then unify them? > > > > > > > > -- > > > > > > > > *Regards,Rohan* > > > > > > > > > -- > > > > *Regards,Rohan Kasat* > > > -- *Regards,Rohan Kasat*
