[
https://issues.apache.org/jira/browse/SOLR-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392059#comment-16392059
]
David Smiley commented on SOLR-11617:
-------------------------------------
Further unifications sounds good, again for 8.x. For now lets try to have
consistent names in the API.
* (v1) "MODIFYALIAS" -> "ALIASPROP".
* (v2) "modify-alias" -> "set-alias-property". "metadata" -> "properties" json
object. Note that the collection property mechanism is defined on
{{collections.collection.Commands.json}} whereas modify-alias is defined on
{{collections.Commands.json}} -- pretty confusing.
* (SolrJ) CollectionAdminRequest.modifyAlias -> setAliasProperty. Harmonize
methods a bit more to that of setCollectionProperty.
* rename "metadata.\*" prefix parameters to "property.\*" v1 and in v2
"properties" parent object
* edit pertinent documentation to refer to "property" or "properties" instead
of "metadata". A parenthetical mention that properties are metadata is
helpful, but we shall call them properties.
That's about as much as we can handle right now.
The paint is still wet on SOLR-11960, so to speak. Before it's API gets set in
stone (by a 7.3 release), perhaps now is the last moment to give the API more
of a bulk parameter feel (like here for aliases) instead of limited to one at a
time? Even if the code can only handle one pair right now, at least the API
would be what we want it to be.
BTW the solr config API itself has "properties" too :-) "set-property" and
"unset-property" v2.
[~romseygeek] (7.3 RM) it's pretty important we do a little something here for
7.3. Bare minimum is we put "experimental" warnings both here (for alias
metadata/properties) and SOLR-11960 (collection properties), or perhaps we can
do a bit better for our users sake.
> Expose Alias Metadata CRUD in REST API
> --------------------------------------
>
> Key: SOLR-11617
> URL: https://issues.apache.org/jira/browse/SOLR-11617
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: master (8.0)
> Reporter: Gus Heck
> Assignee: David Smiley
> Priority: Major
> Fix For: 7.3
>
> Attachments: SOLR_11617.patch, SOLR_11617.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SOLR-11487 is adding Java API for metadata on aliases, this task is to expose
> that functionality to end-users via a REST API.
> Some proposed commands, for initial discussion:
> - *SETALIASMETA* - upsert, or delete if blank/null/white-space provided.
> - *GETALIASMETA* - read existing alias metadata
> Given that the parent ticket to this task is going to rely on the alias
> metadata, and I suspect a user would potentially completely break their time
> partitioned data configuration by editing system metadata directly, we should
> either document these commands as "use at your own risk, great
> power/responsibility etc" or consider protecting some subset of metadata.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
