[
https://issues.apache.org/jira/browse/SOLR-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646303#comment-14646303
]
Timothy Potter commented on SOLR-5606:
--------------------------------------
POST to {{/solr/admin/collections/gettingstarted/shards/shard1/replicas}} is
good for REST aficionados but that's different than how the new bulk-style
schema and config APIs work. The bulk style APIs work off the concept of a
coarse-grained resource (collection, schema, config) and then apply one or more
operations on that resource depending on what's in the request body. Both
approaches have pros and cons. Seems weird to have two different styles in
Solr's "new" API. In other words, breaking the collection API down into
fine-grained sub-resources but then having the bulk approach for schema &
configs seems awkward at best. If we go the REST route, then I'd advocate for
going all-in with HATEOS to help users navigate through all the sub-resources.
> 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]
