Great to know. Thank you very much for your assistance!
On Tue, Jan 12, 2016 at 10:34 AM, Erick Erickson
wrote:
> bq: Do you know, is using the API the
> recommended way of handling collections? As opposed to putting collection
> folders containing "core.properties" file and "conf" folders (cont
bq: Do you know, is using the API the
recommended way of handling collections? As opposed to putting collection
folders containing "core.properties" file and "conf" folders (containing
"schema.xml" and "solrconfig.xml", etc) all in the Solr home location?
Absolutely and certainly DO use the collec
As an update, I went ahead and used the Collection API and deleted the
existing one, and then recreated it (specifying the compositeId router),
and when I tried out MRIT, I didn't have any problems whatsoever with the
number of reducers (and was able to cut the indexing time by over half!!).
I'm gu
I'm actually not specifying any router, and assumed the "implicit" one was
the default. The only resource I can find for setting the document router
is when creating a new collection via the Collections API, which I am not
using. What I do is define several options in the "solrconfig.xml" file,
the
Hmm, it looks like you created your collection with the "implicit"
router. Does the same thing happen when you use the default
compositeId router?
Note, this should be OK with either, this is just to gather more info.
Other questions:
1> Are you running MRIT over Solr indexes that are actually ho
