[
https://issues.apache.org/jira/browse/HADOOP-10611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014229#comment-14014229
]
Andrew Wang commented on HADOOP-10611:
--------------------------------------
I'd like if we tackled this for the common classes too for consistency. It'd be
nice to do something like make {{buildVersionName}} abstract and provide the
current impl as a static helper in e.g. {{KeyProviderUtils}} as Tucu proposed.
I'm not sure exactly what method signature these third-party key providers need
though. Is there a JIRA for this?
+1 for the KMS side stuff though, this part at least looks good.
> KMS, keyVersion name should not be assumed to be keyName@versionNumber
> ----------------------------------------------------------------------
>
> Key: HADOOP-10611
> URL: https://issues.apache.org/jira/browse/HADOOP-10611
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 3.0.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: HADOOP-10611.patch
>
>
> Some KMS classes are assuming the keyVersion is keyName@versionNumber.
> The keyVersion should be handled as an opaque value.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
