[
https://issues.apache.org/jira/browse/HADOOP-10430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971779#comment-13971779
]
Alejandro Abdelnur commented on HADOOP-10430:
---------------------------------------------
The loop as you suggest does 1+N KeyProvider API calls instead just one, that
is what I'm trying to avoid in the case of a KeyProvider client that uses a
remote store.
Also, the Metadata of all keys is not the entire database, it does not include
all the keyversions, just the metadata of each key (cipher, length,
description, created, currentVersion)
The call happens on the KeyShell, which is does a single operation and exits,
so using a bit of more memory it should be fine.
For client applications that are watchful of their memory consumptions, they
can still do the loop as you suggest, the API is still there.
I'm not hang on this, I'd be OK doing the changes you suggest, just that I
think what has been committed has its merits.
> 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)
