[
https://issues.apache.org/jira/browse/HADOOP-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044776#comment-14044776
]
Larry McCay commented on HADOOP-10750:
--------------------------------------
Interesting...
I have a couple high-level comments/questions:
1. if this is a generic cache provider then it would make sense to remove the
KMS part of the name and any dependencies within - if there are any.
2. I'm not sure that I can envision the typical usage pattern for it. In order
for the cache to be meaningful it would have to be used across many access
attempts. This means that it would need to be an instance of the cache provider
(or a backend store of some sort) that lives across multiple usages. I can
easily see how it can be used in a server type environment such as KMS but for
general use it isn't quite as clear. Can you describe the general use that you
have in mind?
> KMSKeyProviderCache should be in hadoop-common
> ----------------------------------------------
>
> Key: HADOOP-10750
> URL: https://issues.apache.org/jira/browse/HADOOP-10750
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 3.0.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
>
> KMS has {{KMSCacheKeyProvider}}, this class should be available in
> hadoop-common for users of {{KeyProvider}} instances to wrap them and avoid
> several, potentially expensive, key retrievals.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
