[
https://issues.apache.org/jira/browse/SOLR-16393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699091#comment-17699091
]
Alex Deparvu edited comment on SOLR-16393 at 3/10/23 7:36 PM:
--------------------------------------------------------------
[~gerlowskija] just checking with you on the Alias Property apis, specifically
the 'set property'
{noformat}
* Set Alias Property
** Current Form: POST /api/collections \{"set-alias-property": {"propName":
"propVal"}}
** Desired Form: PUT /api/aliases/aliasName/properties/propName \{"value":
"someVal"}
{noformat}
I'm wondering if there is one case missing: setting more than a single property
at a time (bulk update). this is possible with current apis.
as far as I can understand the 'properties' value is actually a map
[https://solr.apache.org/guide/solr/latest/deployment-guide/alias-management.html#aliasprop]
but the current proposal only has single value updates.
was (Author: alex.parvulescu):
[~gerlowskija] just checking with you on the Alias Property apis, specifically
the 'set property'
* 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
I'm wondering if there is one case missing: setting more than a single property
at a time (bulk update). this is possible with current apis.
as far as I can understand the 'properties' value is actually a map
[https://solr.apache.org/guide/solr/latest/deployment-guide/alias-management.html#aliasprop]
but the current proposal only has single value updates.
> 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: 3h 20m
> 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, as described in the spreadsheet above.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
