[
https://issues.apache.org/jira/browse/SOLR-12540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896911#comment-17896911
]
Eric Pugh commented on SOLR-12540:
----------------------------------
[~gerlowskija] in the V2 work, don't we have this somewhat better handled? We
have explicit "dev docs" for this, and I'm thinking that we could potentially
close this Jira as "fixed in the V2 apis"???
> 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
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
