You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gus Heck (JIRA)" <ji...@apache.org> on 2017/11/07 20:28:01 UTC
[jira] [Created] (SOLR-11617) Expose Alias Metadata CRUD in REST
API
Gus Heck created SOLR-11617:
-------------------------------
Summary: 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
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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org