[SOLR-11617] Expose Alias Properties CRUD in REST API

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 8.0
• Fix Version/s: 7.3
• Component/s: SolrCloud
• Assignee: David Smiley
• Reporter: Gus Heck
• Created: 07/Nov/17 20:27
• Updated: 02/Oct/19 17:30
• Resolved: 12/Mar/18 14:42

Description

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.

Issue Links

• is related to: SOLR-11691 v2 api for CREATEALIAS fails if given a list with more than one element
• is related to: SOLR-11960 Add collection level properties
• requires: SOLR-11487 Collection Alias metadata for time partitioned collections
• links to: GitHub Pull Request #310
• links to: GitHub Pull Request #310
• links to: GitHub Pull Request #335
• links to: GitHub Pull Request #335