[
https://issues.apache.org/jira/browse/SOLR-11028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617163#comment-17617163
]
Eric Pugh commented on SOLR-11028:
----------------------------------
Can you share your thinking? In general, REST principles are that if an
operation changes things, then it shouldn't be a GET.. I never can remember
if it's PUT or POST.. I think ones a create and ones an update ;-). The
V1 api's were, well, REST like..... But everything ended up being a GET
because folks liked the ability to use the browser as teh api!
Looking forward, I'd like all the operations that we have in the API to also be
exposed in the Solr Admin GUI, so you aren't forced to jam a million parameters
on the browser URL line! Even if the admin gui is just a big chunk of JSON
that you send, not a proper UI....
> Create a v2 API equivalent for REPLACENODE API
> ----------------------------------------------
>
> Key: SOLR-11028
> URL: https://issues.apache.org/jira/browse/SOLR-11028
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, v2 API
> Reporter: Shalin Shekhar Mangar
> Priority: Major
>
> The REPLACENODE API is only implemented as part of the v1 collections API.
> There should be an equivalent call in the v2 paradigm.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
