[
https://issues.apache.org/jira/browse/SOLR-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432152#comment-17432152
]
Chris M. Hostetter commented on SOLR-15709:
-------------------------------------------
Strawman suggestion for how we might be able to "fix" the API to be more CRUD
like in a backcompat way:
(only thinking about the surface API, haven't looked closely into how
complicated changing the internals would be, particularly around the way the V2
API maps to the existing commands)
* Add an {{UPDATE}} action
** this should work basically the same as {{UPLOAD}} currently works, except...
*** A configset with the specified {{name}} *MUST* already exist
*** if {{overwrite=false}} is specified, that should cause a server unless
{{filePath}} is used
* Expand {{CREATE}} to support uploading new configset _OR_ cloning from
existing configset
** if {{baseConfigSet}} name is NOT set, then there MUST be a POST payload
containing the zip file to use to create the configset
** if {{baseConfigSet}} name is set, then there must NOT be a POST payload and
we clone the base config set
* deprecate the {{UPLOAD}} action
> Fix ConfigSet API to be more CRUD like: action=CREATE should be able to
> create, not just CLONE
> ----------------------------------------------------------------------------------------------
>
> Key: SOLR-15709
> URL: https://issues.apache.org/jira/browse/SOLR-15709
> Project: Solr
> Issue Type: Sub-task
> Reporter: Chris M. Hostetter
> Priority: Major
>
> See parent task SOLR-15701 for context.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
