[
https://issues.apache.org/jira/browse/SOLR-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266281#comment-16266281
]
Gus Heck edited comment on SOLR-11617 at 11/27/17 1:05 AM:
-----------------------------------------------------------
Patch implementing MODIFYALIAS and returning a "metadata" section along side
the existing "aliases" section. One minor quirk is that if you remove all alias
metadata from an alias it still shows up with an empty metadata section like
this:
{code:java}
{
"responseHeader":{
"status":0,
"QTime":6},
"aliases":{
"name":"test1,test2",
"name1":"test1,test2"},
"metadata":{
"name":{},
"name1":{"foo":"bar2"}}}
{code}
I'm not sure if that's really such a bad thing though. The metadata section for
the alias is of course still removed if the alias is removed.
V2 stuff not yet contemplated...
was (Author: gus_heck):
Patch implementing MODIFYALIAS and returning a "metadata" section along side
the existing "aliases" section. One minor quirk is that if you remove all alias
metadata from an alias it still shows up with an empty metadata section like
this:
{code:java}
{
"responseHeader":{
"status":0,
"QTime":6},
"aliases":{
"name":"test1,test2",
"name1":"test1,test2"},
"metadata":{
"name":{},
"name1":{"foo":"bar2"}}}
{code}
I'm not sure if that's really such a bad thing though. The metadata section for
the alias is of course still removed if the alias is removed.
> 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
> Attachments: 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
