[
https://issues.apache.org/jira/browse/SOLR-16390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119682#comment-18119682
]
Eric Pugh commented on SOLR-16390:
----------------------------------
I think it works really well when someone is the Jira "gardener" and makign
sure the tickets get to done, and they get closed out, or deleted when things
become OBE. IN the v2 story, we don't need ALL the tickets at once, we need
enough that people know "what is next"....
> Cosmetic improvements and migration to JAX-RS (v2 cluster and clusterprop
> APIs)
> -------------------------------------------------------------------------------
>
> Key: SOLR-16390
> URL: https://issues.apache.org/jira/browse/SOLR-16390
> Project: Solr
> Issue Type: Sub-task
> Components: documentation, v2 API
> Affects Versions: 10.0
> Reporter: Jason Gerlowski
> Priority: Major
> Labels: newdev, pull-request-available
> Time Spent: 6.5h
> 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.
> This ticket plans to tackle making the changes required for Solr's "Cluster"
> and "cluster-prop" APIs. These APIs are described in detail in the
> spreadsheet linked above, but are summarized in the table below for
> convenience and easier tracking.
> 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.)
> *Cosmetic Changes and JAX-RS Conversion*
> ||API Name||Original Form||Desired Form||Status||Volunteer||
> |-Upsert ClusterProp-|-POST /api/cluster \{"set-property": \{...\}\}-|-PUT
> /api/cluster/properties/propName \{"value": "propVal"\}-|-Closed-|-Jason-|
> |-Upsert ClusterProp (Potentially Nested)-|-POST /api/cluster
> \{"set-obj-property": \{...\}\}-|-PUT /api/cluster/properties
> \{...\}-|-Closed-|-Jason-|
> |-Delete ClusterProp-|-POST /api/cluster \{"set-property": \{"name": "foo",
> "value": ""\}\}-|-DELETE /api/cluster/properties/propName-|-Closed-|-Jason-|
> |Delete Single Async Status|DELETE /api/cluster/command-status/123|DELETE
> /api/cluster/commands/123|Open|N/A|
> |Delete All Async Status|DELETE /api/cluster/command-status|DELETE
> /api/cluster/commands|Open|N/A|
> |Get Single Async Status|GET /api/cluster/command-status/123|GET
> /api/cluster/commands/123|Open|N/A|
> |Create rate-limiter|POST /api/cluster/ \{"set-ratelimiter": \{...\}\}|POST
> /api/cluster/ratelimiter \{...\}|Open|N/A|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
