[
https://issues.apache.org/jira/browse/HADOOP-10430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968061#comment-13968061
]
Alejandro Abdelnur commented on HADOOP-10430:
---------------------------------------------
[~owen.omalley], {{KeyProvider}} has a concrete implementation of the method
{{getKeysMetadata()}} and that method uses the abstract methods {{getKeys()}}
and {{getMedataData(String)}}. Implementations of {{KeyProvider}} don't need to
implement {{getKeysMetadata()}}, but they can. A reason to do so is, in the
case of a remote server holding the keys, to reduce the number of RPC calls.
Such overriding is fine if the semantics is preserved, it is an optimization.
From the {{KeyShell}} perspective this does not matter, and if the {{KeyShell}}
uses the {{getKeysMetadata()}} method (as committed), it will benefit from such
optimization for KeyProviders that do so.
> KeyProvider Metadata should have an optional description, 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
> Fix For: 3.0.0
>
> Attachments: HADOOP-10430.patch, HADOOP-10430.patch,
> HADOOP-10430.patch, HADOOP-10430.patch
>
>
> Being able to attach an optional description (and show it when displaying
> metadata) will enable giving some context on the keys.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
