Re: Child=true does not work for data import handler

But in my case i see output as below 0 0 *:* on xml 1533734431931 IT 1 1 1608130338704326656 Data 1 2 1608130338704326656 omkar 1 1608130338704326656 ITI 2 3 1608130338712715264 Entry 2

Re: Child=true does not work for data import handler

This is how nested docs look like. These are document blocks with parent in the end. Block Join Queries work on these blocks. On Wed, Aug 8, 2018 at 12:47 PM omp...@rediffmail.com < omkar.pra...@gmail.com> wrote: > Thanks a lot Mikhail. But as per documentation below nested document > ingestion i

Re: Child=true does not work for data import handler

Thanks a lot Mikhail. But as per documentation below nested document ingestion is possible. Is this limitation of DIH? https://lucene.apache.org/solr/guide/6_6/uploading-data-with-index-handlers.html#UploadingDatawithIndexHandlers-NestedChildDocuments Also can block join query be used to get exp

Re: Child=true does not work for data import handler

It never works like you expect. You need to search for parents and then hook up [child]. I see some improvements are coming, but now that is. On Mon, Aug 6, 2018 at 9:11 PM omp...@rediffmail.com wrote: > Thanks Mikhail verbose did help. _root_ field was missing in schema also in > make some chan

Re: Child=true does not work for data import handler

Thanks Mikhail verbose did help. _root_ field was missing in schema also in make some changes in child entity. Like i created id as alias to emp_id ( in child query) which is id column of parent table.

Re: Child=true does not work for data import handler

DIH has debug&verbose modes. Have you tried to use them? On Mon, Aug 6, 2018 at 4:11 PM omp...@rediffmail.com wrote: > Thanks Mikhail, i tried changing conf but that did not help > > > driver="com.mysql.jdbc.Driver" > url="jdbc:mysql://localhost:3306/test" >

Re: Child=true does not work for data import handler

Thanks Mikhail, i tried changing conf but that did not help

Re: Child=true does not work for data import handler

Hi, Omkar. Could it happen that child docs as well as parents are assigned same "id" field values implicitly and removed due to uniqueKey collision? On Sat, Aug 4, 2018 at 10:12 PM omkar.pra...@gmail.com < omkar.pra...@gmail.com> wrote: > I am using similar db-data config as below for indexing t

Child=true does not work for data import handler

I am using similar db-data config as below for indexing this parent-child data. solr version 6.6.2 SELECT id as emp_id, name FROM emp; +++ | emp_id | name | +++ | 1 | omkar | | 2 | ashwin | +++ 2 rows in set (0.00 sec) select * fro