You may wanna to checkout below these options as well

https://cwiki.apache.org/confluence/display/solr/Advanced+Distributed+Request+Options

https://cwiki.apache.org/confluence/display/solr/Streaming+Expressions#StreamingExpressions-innerJoin


On Fri, Oct 21, 2016 at 7:49 AM, Adi <adise...@gmail.com> wrote:

> Hi,
> Check documentation on join parser,
> https://cwiki.apache.org/confluence/display/solr/Other+
> Parsers#OtherParsers-JoinQueryParser
> Regards,
> Adi
>
> On Fri, Oct 21, 2016, 5:11 PM Preeti Bhat <preeti.b...@shoregrp.com>
> wrote:
>
> > Hi All,
> >
> > I have an requirement where in SQL we have two different sets of data
> like
> > Company and Contact in SQL.
> > We are planning to get this to SOLR, I wanted to know whether we can have
> > two separate collections in SOLR and say have a link between them with
> say
> > id of one collection or if there any better way to get this done. Can we
> > query this data directly?
> >
> > I am searching by say below fields.
> >
> > ? Company ID  -> Get all the contacts linked to this?
> >
> > ? Contact ID-> Get all details of the company linked to this contact
> along
> > with contact details.
> >
> > Could someone suggest if there is any expected impact on performance
> while
> > indexing  or searching?
> >
> > Thanks and Regards,
> > Preeti Bhat
> >
> >
> > NOTICE TO RECIPIENTS: This communication may contain confidential and/or
> > privileged information. If you are not the intended recipient (or have
> > received this communication in error) please notify the sender and
> > it-supp...@shoregrp.com immediately, and destroy this communication. Any
> > unauthorized copying, disclosure or distribution of the material in this
> > communication is strictly forbidden. Any views or opinions presented in
> > this email are solely those of the author and do not necessarily
> represent
> > those of the company. Finally, the recipient should check this email and
> > any attachments for the presence of viruses. The company accepts no
> > liability for any damage caused by any virus transmitted by this email.
> >
> >
> >
>

Reply via email to