lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-11617) Expose Alias Metadata CRUD in REST API
Date Tue, 06 Feb 2018 04:46:02 GMT


ASF subversion and git services commented on SOLR-11617:

Commit 812d400807bcebc782f85dcf3bba5619421880cb in lucene-solr's branch refs/heads/master
from [~dsmiley]
[;h=812d400 ]

SOLR-11722 SOLR-11617: Alias tests: Ensure zkStateReader's view is up to date before acting

> Expose Alias Metadata CRUD in REST API
> --------------------------------------
>                 Key: SOLR-11617
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message