The solution was to delete the tlog. Although it was not very big, it seemed
to be caught-up on a previous indexing error and that kept trying to load.
Many thanks again.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-DIH-from-MySQL-with-unique-ID-tp4214872p4215246
est configured for that. I use terms component
> for autocomplete.
>
> 3. The MySQL query runs very fast, and if I index the largest collection (2
> million documents) alone, it runs in 15 minutes.
>
> Thanks
>
> K
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-DIH-from-MySQL-with-unique-ID-tp4214872p4214946.html
> Sent from the Solr - User mailing list archive at Nabble.com.
http://lucene.472066.n3.nabble.com/Solr-DIH-from-MySQL-with-unique-ID-tp4214872p4214946.html
Sent from the Solr - User mailing list archive at Nabble.com.
gt; book_id AS id
> book_id AS 'id'
>
> and adding pk="book_id" to the entity.
>
> While I'm trying to fix this problem, I also do not understand
>
> 1. Does Solr require that the unique key for a collection must be " id ", or
> can it be any name, such as "book_id"?
>
> Any help or guidance would be appreciated.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-DIH-from-MySQL-with-unique-ID-tp4214872.html
> Sent from the Solr - User mailing list archive at Nabble.com.
uot;?
Any help or guidance would be appreciated.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-DIH-from-MySQL-with-unique-ID-tp4214872.html
Sent from the Solr - User mailing list archive at Nabble.com.
