[
https://issues.apache.org/jira/browse/SOLR-12540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534231#comment-16534231
]
Shawn Heisey commented on SOLR-12540:
-------------------------------------
My personal preference would be the dot-separated notation, normally all
lowercase, and not case-sensitive ... but I wouldn't have a problem with camel
case, as long as it is consistently used.
Eliminating case sensitivity either way would be really nice.
> Solr API - standardize parameter names to either camel case or dot-separated
> lowercase
> --------------------------------------------------------------------------------------
>
> Key: SOLR-12540
> URL: https://issues.apache.org/jira/browse/SOLR-12540
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.4
> Reporter: Shawn Heisey
> Priority: Major
>
> Parameter names for the Solr API are a mixture of camel case and
> dot-separated notation. Here's an API that uses both notations:
> https://lucene.apache.org/solr/guide/7_4/collections-api.html#create-parameters
> That API even has parameters that use both forms at the same time:
> createNodeSet.shuffle and collection.configName are examples.
> We need to standardize on one notation, simplify the names where possible,
> and deprecate non-conforming parameters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
