[
https://issues.apache.org/jira/browse/SOLR-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394358#comment-16394358
]
David Smiley commented on SOLR-11617:
-------------------------------------
BTW Gus added a new PR for the renames (it's auto-linked thanks to JIRA-GitHub
integration). Next time please comment here so Watchers get notified.
> 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: 1h 10m
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
