Hi Guys

Just a quick question on search and join:

I have a few cores which is based on a mainframe extract, 1 core per extracted 
file which resembles a "DB Table"
The cores are all somehow linked via 1 to many fields, with a structure similar 
to a normal ERD

Is it possible to return the result from a query that joins lets say 3 cores in 
the following format:

        "core1_id":"XXX",
        "_childDocuments_":[
        {
          "core2_id":"yyy",
          "core_2_fieldx":"ABC",
                  "_childDocuments_":[
                  {
                    "core3_id":"zzz",
                    "core_3_fieldx":"ABC",
                    "core3_fieldy":"123",
                  {
          "core2_fieldy":"123",
        {

Regards
Moenieb Davids

-----Original Message-----
From: nabil Kouici [mailto:koui...@yahoo.fr.INVALID] 
Sent: 20 January 2017 03:43 PM
To: solr-user@lucene.apache.org
Subject: Re: Joining Across Collections

Hi Mikhail,
I'm not we can do a negation because Field1 and Field2 are not in the join 
condition.
Regards,Nabil.

      De : Mikhail Khludnev <m...@apache.org>
 À : solr-user <solr-user@lucene.apache.org>; nabil Kouici <koui...@yahoo.fr> 
 Envoyé le : Jeudi 19 janvier 2017 9h00
 Objet : Re: Joining Across Collections
   
It seems like it can be done by just negating join query or I'm missing
something.

On Wed, Jan 18, 2017 at 11:32 AM, nabil Kouici <koui...@yahoo.fr.invalid>
wrote:

> Hi All,
> I'm using  join across collection feature to do an inner join between 2
> collections. It works fine.
> Is it possible to use this feature to compare between fields from
> different collections. For exemple:
> Collection1 Field1Collection2 Field2
> search document from Collection1 where Field1 != Field2
> In sql, this will translated to:
> Select A.* From Collection1 A inner join Collection2 B on  A.id=B.idWhere
> A.Field1<>B.Field2
>
> Thank you.
> Regards,NKI.
>



-- 
Sincerely yours
Mikhail Khludnev


   










===========================================================================
GPAA e-mail Disclaimers and confidential note 

This e-mail is intended for the exclusive use of the addressee only.
If you are not the intended recipient, you should not use the contents 
or disclose them to any other person. Please notify the sender immediately 
and delete the e-mail. This e-mail is not intended nor 
shall it be taken to create any legal relations, contractual or otherwise. 
Legally binding obligations can only arise for the GPAA by means of 
a written instrument signed by an authorised signatory.
===========================================================================

Reply via email to