Well, you can do Entities within Entities and all of that hierarchical
matching will go into a single document (unless you use child=true
flag).

But there is nothing that supports random number of deep levels. And,
given the complexity, I still would keep away from using DIH for such
use case.

Regards,
   Alex.

On Tue, 30 Apr 2019 at 07:54, Srinivas Kashyap <srini...@bamboorose.com> wrote:
>
> Hi Alexandre,
>
> Yes, the whole tree gets mapped to and returned as single flat document. When 
> you search, it should return all the matching documents if it matches that 
> nested field.
>
> Thanks and Regards,
> Srinivas Kashyap
>
> -----Original Message-----
> From: Alexandre Rafalovitch <arafa...@gmail.com>
> Sent: 30 April 2019 05:06 PM
> To: solr-user <solr-user@lucene.apache.org>
> Subject: Re: multi-level Nested entities in dih
>
> DIH may not be able to do arbitrary nesting. And it is not recommended for 
> complex production cases.
>
> However, in general, you also have to focus on what your _search_ will look 
> like. Amd only then think about the mapping.
>
> For example, is that whole tree gets mapped to and returned as a single flat 
> document of fields? Or gets mapped to multiple result documents?
>
> Regards,
>      Alex
>
> On Tue, Apr 30, 2019, 6:29 AM Srinivas Kashyap, <srini...@bamboorose.com>
> wrote:
>
> > Hello,
> >
> > I'm using DIH to index the data using SQL. I have requirement as shown
> > below:
> >
> > Parent entity
> >                 Child1
> >                 Child2
> >                 Child3
> >                 CHILD4( child41, child42, CHILD43(child
> > 431,child432,child433,CHILD434...)
> >
> > How to recursively iterate the child entities which have some more
> > child entities in them until I'm done with all the children.
> >
> > Thanks and Regards,
> > Srinivas Kashyap
> > ________________________________
> > DISCLAIMER:
> > E-mails and attachments from Bamboo Rose, LLC are confidential.
> > If you are not the intended recipient, please notify the sender
> > immediately by replying to the e-mail, and then delete it without
> > making copies or using it in any way.
> > No representation is made that this email or any attachments are free
> > of viruses. Virus scanning is recommended and is the responsibility of
> > the recipient.
> >

Reply via email to