[
https://issues.apache.org/jira/browse/HADOOP-10841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064643#comment-14064643
]
Hadoop QA commented on HADOOP-10841:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12656223/HADOOP-10841.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 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common:
org.apache.hadoop.fs.TestSymlinkLocalFSFileSystem
org.apache.hadoop.fs.TestSymlinkLocalFSFileContext
org.apache.hadoop.ipc.TestIPC
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4302//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4302//console
This message is automatically generated.
> EncryptedKeyVersion should have a key name property
> ---------------------------------------------------
>
> Key: HADOOP-10841
> URL: https://issues.apache.org/jira/browse/HADOOP-10841
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 3.0.0
> Reporter: Alejandro Abdelnur
> Assignee: Arun Suresh
> Attachments: HADOOP-10841.1.patch
>
>
> having a keyname will help the NN to efficiently (without additional
> keyprovider calls, which can translate into remote calls) determine the key
> name of an EDEK.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
