[
https://issues.apache.org/jira/browse/SOLR-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646282#comment-14646282
]
Steve Molloy commented on SOLR-5606:
------------------------------------
Makes sense. Basically, what I'm trying to get at is that action to be
performed should not be part of query parameters (or POST body which is pretty
much the same). It should be represented by the HTTP method used as much as
possible, POST to create, PUT to modify, GET to list/retrieve info, DELETE to
delete. There are some operations that cannot fit this, but we should go that
route when possible.
> 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]
