[
https://issues.apache.org/jira/browse/SOLR-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645950#comment-14645950
]
Steve Molloy commented on SOLR-5606:
------------------------------------
I guess others have already replied, but just to make sure my comment is not
perceived as contradictory... I don't have an issue with
/solr/admin/collections, /solr/admin/cores, etc. I think it actually makes a
lot of sense. I wasn't debating about the actual endpoint but rather about the
fact that the endpoint could work with multiple resource types with that "type"
parameter. So last comment by [~noble.paul] makes perfect sense to me.
Basically, /solr/admin/collections would manage collections, while
/solr/{collection}/{handler} would work with documents in it, so it makes sense
to have them separate.
> 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]
