[
https://issues.apache.org/jira/browse/SOLR-16393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700706#comment-17700706
]
ASF subversion and git services commented on SOLR-16393:
--------------------------------------------------------
Commit 52504fa27dd5f603e74b10e84e0ff830c55c9fc3 in solr's branch
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=52504fa27dd ]
SOLR-16393: Migrate alias-deletion to JAX-RS (#1452)
This commit makes various cosmetic improvements to Solr's v2 delete
alias API, to bring it more into line with the more REST-ful v2
design. In the process it also converts the API to the JAX-RS
framework.
As of this commit, the delete-alias API is now
- DELETE /api/aliases/aliasName
> Cosmetic improvements and migration to JAX-RS (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
> Assignee: Jason Gerlowski
> Priority: Major
> Labels: newdev
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> 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.
> While we're touching the code for these endpoints, we should also convert
> them to JAX-RS framework definitions. (This was initially tracked as a
> separate effort - see SOLR-16370 - but the edit that were required ended up
> overlapping so significantly with the "cosmetic" improvements here that in
> practice it almost always makes sense to do the two together.)
> This ticket plans to tackle making the changes required for Solr's alias and
> alias-prop CRUD APIs. These are described in detail in the spreadsheet
> linked above, but are summarized in the table below for convenience and
> easier tracking.
> ||API Name||Original Form||Desired Form||Status||Volunteer||
> |-List Alias-|-GET /api/cluster/aliases-|-GET /api/aliases-|-Finished-|-Alex-|
> |Create Alias|POST /api/collections \{"create-alias": \{...\}\}|POST
> /api/aliases {...}|Open|N/A|
> |Delete Alias|POST /api/collections \{"delete-alias": \{...\}\}|DELETE
> /api/aliases/aliasName|Open|Jason|
> |Set Alias Property|POST /api/collections \{"set-alias-property":
> \{...\}\}|PUT /api/aliases/aliasName/properties/propName {"value":
> "someVal"}|Open|Alex|
> |Delete Alias Property|POST /api/collections \{"set-alias-property":
> \{"propName": ""\}\}|DELETE
> /api/aliases/aliasName/properties/propName|Open|Alex|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
