[ 
https://issues.apache.org/jira/browse/HADOOP-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050508#comment-14050508
 ] 

Hadoop QA commented on HADOOP-10757:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12653624/HADOOP-10757.1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/4199//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/4199//console

This message is automatically generated.

> KeyProvider KeyVersion should provide the key name
> --------------------------------------------------
>
>                 Key: HADOOP-10757
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10757
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 3.0.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Arun Suresh
>         Attachments: HADOOP-10757.1.patch
>
>
> Currently the {{KeyVersion}} does not provide a way to get the key name to do 
> a reverse lookup to get the metadata of the key.
> For the {{JavaKeyStoreProvider}} and the {{UserProvider}} this is not an 
> issue because the key name is encoded in the key version name. 
> This encoding of the key name in the key version name cannot be expected in 
> all KeyProvider implementations. It is common for key management systems to 
> use UUID to refer to specific key materials (KeyVersions in Hadoop parlance).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to