[
https://issues.apache.org/jira/browse/SOLR-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645179#comment-14645179
]
Timothy Potter commented on SOLR-5606:
--------------------------------------
[~smolloy] what's your proposal for how to get a list of collections? If I'm
reading this statement correctly:
bq. Not only is it cleaner to have the resource you want to interact with part
of the URL used to access it, it would also make it much easier to integrate
with standard client libraries for REST APIs.
Sounds like you want the API to get a list of collections to be at endpoint
{{/solr/collections}} and when addressing a specific collection
{{/solr/collections/<collection>/[query|update|admin|whatever]}}
Noble proposed hanging the list of collections off of {{/solr}} to avoid this
issue, which I'm fine with and also POST'ing to {{/solr}} to create a
collection (with the correct JSON params in the request body of course).
Without the type parameter, we either have to say {{/solr}} always deals with
collections only and any other types have their own unique path, such as
{{/solr/cores}}. If we want {{/solr/collections/}} in every path that addresses
anything collection related, then I'm not going to argue ... just want to be
clear.
> REST based Collections API
> --------------------------
>
> Key: SOLR-5606
> URL: https://issues.apache.org/jira/browse/SOLR-5606
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Jan Høydahl
> Priority: Minor
> Fix For: Trunk
>
>
> For consistency reasons, the collections API (and other admin APIs) should be
> REST based. Spinoff from SOLR-1523
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
