Shawn's point (and JIRA) is that the UI doesn't pass the "router"
parameter correctly, so it is being ignored.
Simply put: You cannot create collections with the admin UI using
implicit routing because of this bug. Don't use it.
Either use the "solr/bin create_collection" command or put the
Hello Shawn,
Here are the UI options i filled and for more clarification i am using
solr 6.5.1
name : Collection_name
config set: ber
numshards: 1
replicationfactor: 1
Advance options:
router : Implicit
maxShardPerNode: 1
shards: 20180111_04,20180111_05
routerField: dateandhour
Regards
On 1/10/2018 11:00 PM, manish tanger wrote:
As we are connecting through zookeeper my understanding was routing will
done by a zookeeper, Thanks for the clarification.
CloudSolrClient doesn't actually connect through ZK. When you create
the client using ZK info, the client reads information
On 1/10/2018 12:18 AM, manish tanger wrote:
I am having a doubt in implicit routing and didn't find much info about
this over the internet, so Please help me out on this.
*About environment:*
M/c 1: Zookeeper 1 and Solr 1
M/c 2: Zookeeper 2 and Solr 2
For redundancy with ZK, you need three
Hello Solr-dev folks,
I am having a doubt in implicit routing and didn't find much info about
this over the internet, so Please help me out on this.
*About environment:*
M/c 1: Zookeeper 1 and Solr 1
M/c 2: Zookeeper 2 and Solr 2
I am using clustered zookeeper and using "CloudSolrClient" from
Hello All,
I am having a doubt in implicit routing and didn't find much info about
this over the internet, so Please help me out on this.
*About environment:*
M/c 1: Zookeeper 1 and Solr 1
M/c 2: Zookeeper 2 and Solr 2
I am using clustered zookeeper and using "CloudSolrClient" from solrJ
API in
