[
https://issues.apache.org/jira/browse/SOLR-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329672#comment-16329672
]
Gus Heck commented on SOLR-11617:
---------------------------------
* I don't really want to create two ways to modify aliases (and 2 places to
maintain the functionality) I'll leave MODIFYALIAS as is unless additional
opinions surface.
* I don't think we accept whitespace for collection names etc and I think that
it's not very friendly to make whitespace significant in general. I'm generally
thinking that metadata keys should be trimmed. It would be a very strange use
case to want to be able to set values for keys like ' foo', 'foo ' and ' foo
'.. and much more common for such a thing to result in confusing debugging
sessions. for values, it feel a bit trappy to set a value of ' ' instead of
deleting if the person issuing the command accidentally appends a space...
However, I suppose there's some possibility that someone might want to keep a
metadata property that contained a delimiter and have that delimiter be
whitespace... for values its a trade off i guess. I could go either way.
* multi-properties, yeah that would be good.
* Linked Hash Map (/)
> 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
> Priority: Major
> Attachments: SOLR_11617.patch, SOLR_11617.patch
>
>
> 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]
