[
https://issues.apache.org/jira/browse/SOLR-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645018#comment-14645018
]
Steve Molloy commented on SOLR-5606:
------------------------------------
I agree with pretty much all that is being said, with one big exception on the
"type" parameter. If you want some REST-like API, you should not get different
types of results depending on query parameters. So I'd definitely recommend
keeping the /solr/collection approach, and have /solr/core for cores,
/solr/schema, /solr/alias, etc... All this can live very well with bulk
operations, you could either PUT a single schema to update it, or POST a list
of collection information to create multiple collections in bulk, but on the
right resource type. 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.
> 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]
