[
https://issues.apache.org/jira/browse/SOLR-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067621#comment-14067621
]
Anshum Gupta commented on SOLR-4999:
------------------------------------
Thinking about all the APIs, the name/collection split already mostly makes
sense (logically). This would just help standardize the APIs.
If we decide to do this (which I'm already having split thoughts about), it
would make more sense to break the back-compat with 5.0 and give users an
option to use either for all the 4.x releases. Having both of them work in 5.x
would only make things more confusing and also lead to messy code.
> Make the collections API consistent by using 'collection' instead of 'name'
> ---------------------------------------------------------------------------
>
> Key: SOLR-4999
> URL: https://issues.apache.org/jira/browse/SOLR-4999
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.3.1
> Reporter: Anshum Gupta
>
> The collections API as of now are split between using 'name' and 'collection'
> parameter.
> We should add support to all APIs to work with 'collection', while
> maintaining 'name' (where it already exists) until 5.0.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
