ch one of parent
> tuples and execute the child entity sql’s(with where condition of parent) to
> create one solr document? Won’t it be more load on database by executing more
> sqls? Is there an optimum solution?
>
> Thanks,
> Srinivas
> From: Erick Erickson
> Sent: 22 May 2
22:52
To: solr-user@lucene.apache.org
Subject: Re: Indexing huge data onto solr
You have a lot more control over the speed and form of importing data if
you just do the initial load in SolrJ. Here’s an example, taking the Tika
parts out is easy:
https://lucidworks.com/post/indexing-with-solrj
I can index (without nested entities ofc ;) ) 100M records in about
6-8 hours on a pretty low-powered machine using vanilla DIH -> mysql
so it is probably worth looking at why it is going slow before writing
your own indexer (which we are finally having to do)
On Fri, May 22, 2020 at 1:22 PM Erick
You have a lot more control over the speed and form of importing data if
you just do the initial load in SolrJ. Here’s an example, taking the Tika
parts out is easy:
https://lucidworks.com/post/indexing-with-solrj/
It’s especially instructive to comment out just the call to
CloudSolrClient.add(d
