[
https://issues.apache.org/jira/browse/SOLR-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598016#comment-14598016
]
Erick Erickson commented on SOLR-7132:
--------------------------------------
Makes sense, I may actually get to this this week sometime.
I do like making this obscure via requiring property.name to be specified.
Making the option obvious does more harm than good IMO since it encourages
people to shoot themselves in the foot. But deprecating it as you have done and
allowing this "back door" keeps casual/new users from doing something bad
because they see the "name" option but still allows someone who _really_ cares
to control naming. Not that I'd advise they do so, but you _know_ someone will
want to ;)
> 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]
