You cannot just make configuration changes, whether you use implicit
or compositeId is defined when you _create_ the collection and cannot
be changed later.

You need to create a new collection and specify router.name=implicit
when you create it. Then you can route documents as you desire.

I would caution against this though. If you use implicit routing _you_
have to insure balancing. For instance, you could have 10,000,000
documents for "Org1" and 15 for "Org2", resulting in hugely unbalanced
shards.

Implicit routing is particularly useful for time-series indexing,
where you, say, index a day's worth of documents to each shard. It may
be appropriate in your case, but so far you haven't told us _why_ you
think routing docs to particular shards is desirable.

Best,
Erick

On Thu, Nov 9, 2017 at 10:27 PM, Ketan Thanki <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB