RE: Implicit routing changes to Composite while re-deploy changes and make Upconfig command

2017-12-18 Thread Nimesh Aghera
arted' collection every time which is already exists. So will you please try above scenario. Please do needful. Regards, Nimesh Aghera -Original Message- From: Shawn Heisey [mailto:apa...@elyograg.org] Sent: Thursday, December 14, 2017 8:55 PM To: solr-user@lucene.apache.org S

RE: Implicit routing changes to Composite while re-deploy changes and make Upconfig command

2017-12-13 Thread Nimesh Aghera
st, Erick On Tue, Dec 12, 2017 at 1:15 AM, Nimesh Aghera mailto:nagh...@asite.com>> wrote: > Hello, > > I have implemented implicit routing with below configuration. > Created one default collection manually 'AMS_Config' which contains > configurations

RE: Implicit routing changes to Composite while re-deploy changes and make Upconfig command

2017-12-13 Thread Nimesh Aghera
shows my model collection as below and also it index data across all shards [cid:image003.png@01D37430.873F2130] Its causes issues that if any how its required to make upconfig than it change the routing from implicit to compositeId. Please do needful. Regards, Nimesh Aghera

Implicit routing changes to Composite while re-deploy changes and make Upconfig command

2017-12-12 Thread Nimesh Aghera
/conf -confname AMS_Config -z It will changes the router value implicit to compositeId and now my document are index across all shard so why this should happens.How to avoid this. Please do the needful. Regards, Nimesh Aghera [CC Award Winners!]