[
https://issues.apache.org/jira/browse/SOLR-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597743#comment-14597743
]
Varun Thacker commented on SOLR-7132:
-------------------------------------
Hi Eric,
Yes we could also disallow "property.name" but this is my thinking currently.
We have deprecated the name method for Solr 5.3 in SOLR-7499. We can remove it
in Solr 5.4 . We don't make any changes to disallow "property.name" so that
expert users who really have a use case of specifying the core name can use
this method?
We can still fix the bug that it only changes the name on a restart and not
while creation. What do you think?
> The Collections API ADDREPLICA command property.name is not reflected in the
> clusterstate until after Solr restarts
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-7132
> URL: https://issues.apache.org/jira/browse/SOLR-7132
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.1, Trunk
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
>
> If you do an ADDREPLICA command with &property.name=nonsense then go look at
> clusterstate.json, you'll see the default name for the replica. But if you
> then restart Solr, you see the name you specified on the create command,
> which is a bit confusing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
