[
https://issues.apache.org/jira/browse/SOLR-12540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897185#comment-17897185
]
Jason Gerlowski commented on SOLR-12540:
----------------------------------------
We don't currently have this documented in
{{dev-docs/v2-api-conventions.adoc}}, but I agree that we should.
I've been standardizing on camelCase in practice, so I'd argue that's the "de
facto" winner in v2 at this point. Though if someone has a really strong
argument for kebab or something else, I'm open to that.
bq. we could potentially close this Jira as "fixed in the V2 apis"
I have no objection if someone does have the motivation to go and do this on
our v1 APIs -- it's hard to imagine v1 disappearing any time soon, so I'm sure
that work would be valuable. But given that no one's been motivated in the ~6
years since this ticket was filed, I also don't have any objection to closing
this out (provided that we document the v2 convention as described above). We
can always reopen it later if there's a volunteer interested in seeing this
done.
> 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: [email protected]
For additional commands, e-mail: [email protected]
