[
https://issues.apache.org/jira/browse/HADOOP-10430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963012#comment-13963012
]
Larry McCay commented on HADOOP-10430:
--------------------------------------
Hmmm... I don't think that I agree - though I can potentially see this as a
separate piece of metadata to be introduced in a follow up jira. This way it
doesn't interfere with the simple descriptive goal of this label.
I do think that we should prescribe a simple delimiter for it though - maybe
just space - and the values should be arbitrary.
This allows the apps and tools to uniformly understand how to parse them and
potentially have app specific semantics for evaluating them.
What do you think about separate a jira to introduce a tags metadata field?
> KeyProvider Metadata should have an optional label, there should be a method
> to retrieve the metadata from all keys
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-10430
> URL: https://issues.apache.org/jira/browse/HADOOP-10430
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 3.0.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: HADOOP-10430.patch
>
>
> Being able to attach an optional label (and show it when displaying metadata)
> will enable giving some context on the keys.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
