Thanks John. I got it sorted, but that part you pointed still looks
confusing. Imho it should be "You could also use the _route_ parameter
to name a specific shard*when ingesting documents, so Solrcloud will
route your document to specific shard.*"
Cheers.
On 20/10/16 19:14, John Bickerstaff wrote:
more specifically, this bit from that page seems like it might be of
interest:
If you created the collection and defined the "implicit" router at the time
of creation, you can additionally define a router.field parameter to use a
field from each document to identify a shard where the document belongs. If
the field specified is missing in the document, however, the document will
be rejected. You could also use the _route_ parameter to name a specific
shard.
On Thu, Oct 20, 2016 at 12:12 PM, John Bickerstaff <j...@johnbickerstaff.com
wrote:
This may help? https://cwiki.apache.org/confluence/display/solr/
Shards+and+Indexing+Data+in+SolrCloud
On Thu, Oct 20, 2016 at 12:09 PM, Customer <mailinglists...@gmail.com>
wrote:
Hey,
I hope you all are doing well..
I got a router with "router.name=implicit" with couple of shards (lets
call them shardA and shardB) and got a mysql table ready to import for
testing purposes. So for example I want to load half of the data to shardA
and the rest - to the shardB. Question is - how I can do that ? I thought
this is something to add to the RESTful call when doing import for example
like curl -m 99999 "http://localhost:8983/solr/te
stIMPLICIT2/dataimport?=command=full-import&implicit=shardA , but looks
like I was wrong.
Thanks
