You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Jason Gerlowski (Jira)" <ji...@apache.org> on 2022/10/24 14:33:00 UTC

[jira] [Commented] (SOLR-16393) Cosmetic, REST-fulness improvements to v2 alias, alias-prop CRUD APIs

    [ https://issues.apache.org/jira/browse/SOLR-16393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623216#comment-17623216 ] 

Jason Gerlowski commented on SOLR-16393:
----------------------------------------

To be a little more explicit about the APIs we want this ticket to cover, I found 5 APIs that need work related to alias/aliasprop CRUD:

* List Aliases
** Current Form: GET /api/cluster/aliases
** Desired Form: GET /api/aliases
** Spreadsheet Ref: Tab 1, Line 36
* Create Alias
** Current Form: POST /api/collections \{"create-alias": \{...\}\}
** Desired Form: POST /api/aliases \{...\}
** Spreadsheet Ref: Tab 1, Line 37
* Delete Alias
** Current Form: POST /api/collections \{"delete-alias": \{...\}\}
** Desired Form: DELETE /api/aliases/aliasName
** Spreadsheet Ref: Tab 1, Line 39
* Set Alias Property
** Current Form: POST /api/collections \{"set-alias-property": \{"propName": "propVal"\}\}
** Desired Form: PUT /api/aliases/aliasName/properties/propName \{"value": "someVal"\}
** Spreadsheet Ref: Tab 1, Line 55
* Delete Alias Property
** Current Form: POST /api/collections \{"set-alias-property": \{"propName": ""\}\}
** Desired Form: DELETE /api/aliases/aliasName/properties/propName
** Spreadsheet Ref: Tab 1, Line 58

Obviously this is a big list.  IMO it makes sense to split these up across different PRs, doing some small number (i.e. 1 or 2) of APIs per-PR.  If anyone wants to help chip away at this, just call out which APIs from this list you intend to work on and we can parallelize them.

In terms of the steps required, the JIRA comments [here|https://issues.apache.org/jira/browse/SOLR-15737?focusedCommentId=17617806&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17617806] and [here|https://issues.apache.org/jira/browse/SOLR-15737?focusedCommentId=17617923&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17617923] give some good background and step-by-step instructions for switching APIs over to the new JAX-RS framework, which is usually helpful or even required as the traditional v2 framework doesn't lend itself very readily to RESTful APIs.  (Those comments describe creating a new API "from scratch", but the steps are still applicable to modifying an existing API.)  The PR [here|https://github.com/apache/solr/pull/1053] also serves as a helpful example to work from.

Not all API modifications require the new JAX-RS framework, though it is preferred going forward.  Instructions for updating APIs using the older, traditional v2 framework can be found [here|https://issues.apache.org/jira/browse/SOLR-15737?focusedCommentId=17565076&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17565076], and an example PR can be found [here|https://github.com/apache/solr/pull/1061].

> Cosmetic, REST-fulness improvements to v2 alias, alias-prop CRUD APIs
> ---------------------------------------------------------------------
>
>                 Key: SOLR-16393
>                 URL: https://issues.apache.org/jira/browse/SOLR-16393
>             Project: Solr
>          Issue Type: Sub-task
>          Components: v2 API
>            Reporter: Jason Gerlowski
>            Priority: Major
>
> As mentioned on SOLR-15781, the v2 API currently has an experimental designation, and the community has expressed an interest in using this period to update our v2 endpoints to be more REST-ful and consistent.  The current plan is to follow the
> specific changes laid out in [this spreadsheet|https://docs.google.com/spreadsheets/d/1HAoBBFPpSiT8mJmgNZKkZAPwfCfPvlc08m5jz3fQBpA/edit?usp=sharing], though of course nothing there is set in stone and there are still warts to be worked out.
>  
> This ticket plans to tackle making the changes required for Solr's alias and alias-prop CRUD APIs, as described in the spreadsheet above. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org