[
https://issues.apache.org/jira/browse/SOLR-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644601#comment-14644601
]
Timothy Potter commented on SOLR-5606:
--------------------------------------
thanks for the feedback Mark ...
bq. And the new schema API's were always meant to be the way of the future -
start there, then start moving the other API's more in line with them.
Just to be clear, are you talking about the pure REST APIs for Schema that
Steve Rowe did or the bulk-style Schema API that Noble did? I'm personally a
fan of the bulk operation style vs. addressing every object inside of schema
(or config) as a specific resource.
bq. re: Noble's comment "a GET on http://localhost:8080/solr can respond with
all available collection names"
I'll buy that, but it's a little subtle ... I do think it's important to have a
way to filter collections when requesting the list, so would one just do
something like the following?
{code}
http://localhost:8983/solr?type=collection&filter=name&name=tj*
{code}
The type parameter could default to "collection" but I was thinking having it
could allow us to support other types of resources if needed in the future and
makes the GET request in the example easier to understand.
> 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]
