ASF subversion and git services commented on SOLR-11617:

Commit 9957e0eed2f93cc69abc132ec631a57decd22b77 in lucene-solr's branch 
refs/heads/branch_7x from [~dsmiley]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9957e0e ]

SOLR-11617: rename alias metadata to properties

(cherry picked from commit bf6503b)

> Expose Alias Properties 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 40m
>  Remaining Estimate: 0h
> Note: Aliases metadata is now "properties".   See the Ref Guide for final 
> documentation for V1 {{ALIASPROP}} or V2 introspect on {{set-alias-property}}
> ----
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to