See: https://issues.apache.org/jira/browse/SOLR-6719
It's not clear that we'll support this, so this may just be a doc change. How would you properly support having more than one replica? Or, for that matter, having more than one shard? Property.name would have to do something to make the core names unique. I agree that for single-shard, single replica situations it's a reasonable thing to do, but I'm not at all sure the effort is worth the gain for that one case. Yes, you can create a bunch of rules that would allow you to map selected names to a long, comma separated string or something like that, but it just doesn't seem worth the effort. Best, Erick On Mon, Aug 3, 2015 at 1:48 AM, davidphilip cherian <davidphilipcher...@gmail.com> wrote: > How to use the 'property.name=value' in the api example[1] to modify > core.properties value of 'name' > > While creating the collection with below query[2], the core names become > 'aggregator_shard1_replica1' and 'aggregator_shard2_replica1'. I wanted > have specific/custom name for each of these cores. I tried passing the > params as property.name=name&name=aggregator_s1, but it did not work. > > Editing the core.properties key value pair of name=aggregator_s1 after > collection is created, works! But I was looking for setting this property > with create request itself. > > [2] > http://example.com:8983/solr/admin/collections?action=CREATE&name=aggregator&numShards=1&replicationFactor=2&maxShardsPerNode=1&collection.configName=aggregator_config&property.name=name&name=aggregator_s1 > > [1] > https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api1
