lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gus Heck (JIRA)" <>
Subject [jira] [Commented] (SOLR-11617) Expose Alias Metadata CRUD in REST API
Date Sun, 28 Jan 2018 08:13:00 GMT


Gus Heck commented on SOLR-11617:

Pull request updated, thought that was supposed to result in a message here, but it doesn't
seem to. I removed the parameter for whitespace optionality but also removed the requirement.
As I said above I'm not able to convince myself that there isn't a use case for a value that
is whitespace so If there isn't going to be an option, then we probably should allow it. Tests
& a CollectionAdminRequest method/class were added.

> 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
>            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

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

View raw message