date:20140427

[jira] [Commented] (HADOOP-10521) FsShell commands for extended attributes.

2014-04-27 Thread Uma Maheswara Rao G (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982201#comment-13982201
 ] 

Uma Maheswara Rao G commented on HADOOP-10521:
--

Regarding to Enum#valueOf, how does below code piece look?
Of course guava library does that Illegalargumentexception handling and return 
null to us, if there is no enum value exist.
{code}
private final static FunctionString, ENCODE encodeValueOfFunc = Enums
  .valueOfFunction(ENCODE.class);
.
.
.
if (en != null) {
  encode = encodeValueOfFunc.apply(en);
}
Preconditions.checkArgument(encode != null,
  Invalid/unsupported econding option specified: en= + en);

Test:
 runCommand(new String[] { -getfattr, -e, invalid,-n, xattrname, 
/file1  });
result:
-getfattr: Invalid/unsupported encoding option specified: en=invalid
{code}

 FsShell commands for extended attributes.
 -

 Key: HADOOP-10521
 URL: https://issues.apache.org/jira/browse/HADOOP-10521
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: fs
Affects Versions: HDFS XAttrs (HDFS-2006)
Reporter: Yi Liu
Assignee: Yi Liu
 Attachments: HADOOP-10521.1.patch, HADOOP-10521.2.patch, 
 HADOOP-10521.3.patch, HADOOP-10521.patch


 “setfattr” and “getfattr” commands are added to FsShell for XAttr, and these 
 are the same as in Linux.



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

[jira] [Comment Edited] (HADOOP-10521) FsShell commands for extended attributes.

2014-04-27 Thread Uma Maheswara Rao G (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982201#comment-13982201
 ] 

Uma Maheswara Rao G edited comment on HADOOP-10521 at 4/27/14 6:27 AM:
---

Regarding to Enum#valueOf, how does below code piece look?
Of course guava library does that Illegalargumentexception handling and return 
null to us, if there is no enum value exist.
{code}
private final static FunctionString, ENCODE encodeValueOfFunc = Enums
  .valueOfFunction(ENCODE.class);
.
.
.
if (en != null) {
  encode = encodeValueOfFunc.apply(en);
}
Preconditions.checkArgument(encode != null,
  Invalid/unsupported econding option specified: en= + en);

Test:
 runCommand(new String[] { -getfattr, -e, invalid,-n, xattrname, 
/file1  });
result:
-getfattr: Invalid/unsupported encoding option specified: en=invalid
{code}

tiny nit: 
Can not specify both '-n name' and '-x name' *option.* -- Can not specify 
both '-n name' and '-x name' *options.* ?


was (Author: umamaheswararao):
Regarding to Enum#valueOf, how does below code piece look?
Of course guava library does that Illegalargumentexception handling and return 
null to us, if there is no enum value exist.
{code}
private final static FunctionString, ENCODE encodeValueOfFunc = Enums
  .valueOfFunction(ENCODE.class);
.
.
.
if (en != null) {
  encode = encodeValueOfFunc.apply(en);
}
Preconditions.checkArgument(encode != null,
  Invalid/unsupported econding option specified: en= + en);

Test:
 runCommand(new String[] { -getfattr, -e, invalid,-n, xattrname, 
/file1  });
result:
-getfattr: Invalid/unsupported encoding option specified: en=invalid
{code}

 FsShell commands for extended attributes.
 -

 Key: HADOOP-10521
 URL: https://issues.apache.org/jira/browse/HADOOP-10521
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: fs
Affects Versions: HDFS XAttrs (HDFS-2006)
Reporter: Yi Liu
Assignee: Yi Liu
 Attachments: HADOOP-10521.1.patch, HADOOP-10521.2.patch, 
 HADOOP-10521.3.patch, HADOOP-10521.patch


 “setfattr” and “getfattr” commands are added to FsShell for XAttr, and these 
 are the same as in Linux.



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

[jira] [Comment Edited] (HADOOP-10521) FsShell commands for extended attributes.

2014-04-27 Thread Uma Maheswara Rao G (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982201#comment-13982201
 ] 

Uma Maheswara Rao G edited comment on HADOOP-10521 at 4/27/14 6:32 AM:
---

Regarding to Enum#valueOf, how does below code piece look?
Of course guava library does that Illegalargumentexception handling and return 
null to us, if there is no enum value exist.
{code}
private final static FunctionString, ENCODE encodeValueOfFunc = Enums
  .valueOfFunction(ENCODE.class);
.
.
.
if (en != null) {
  encode = encodeValueOfFunc.apply(en);
}
Preconditions.checkArgument(encode != null,
  Invalid/unsupported econding option specified: en= + en);

Test:
 runCommand(new String[] { -getfattr, -e, invalid,-n, xattrname, 
/file1  });
result:
-getfattr: Invalid/unsupported encoding option specified: en=invalid
{code}

Also please cover this validation cases in your tests.
tiny nit: 
Can not specify both '-n name' and '-x name' *option.* -- Can not specify 
both '-n name' and '-x name' *options.* ?


was (Author: umamaheswararao):
Regarding to Enum#valueOf, how does below code piece look?
Of course guava library does that Illegalargumentexception handling and return 
null to us, if there is no enum value exist.
{code}
private final static FunctionString, ENCODE encodeValueOfFunc = Enums
  .valueOfFunction(ENCODE.class);
.
.
.
if (en != null) {
  encode = encodeValueOfFunc.apply(en);
}
Preconditions.checkArgument(encode != null,
  Invalid/unsupported econding option specified: en= + en);

Test:
 runCommand(new String[] { -getfattr, -e, invalid,-n, xattrname, 
/file1  });
result:
-getfattr: Invalid/unsupported encoding option specified: en=invalid
{code}

tiny nit: 
Can not specify both '-n name' and '-x name' *option.* -- Can not specify 
both '-n name' and '-x name' *options.* ?

 FsShell commands for extended attributes.
 -

 Key: HADOOP-10521
 URL: https://issues.apache.org/jira/browse/HADOOP-10521
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: fs
Affects Versions: HDFS XAttrs (HDFS-2006)
Reporter: Yi Liu
Assignee: Yi Liu
 Attachments: HADOOP-10521.1.patch, HADOOP-10521.2.patch, 
 HADOOP-10521.3.patch, HADOOP-10521.patch


 “setfattr” and “getfattr” commands are added to FsShell for XAttr, and these 
 are the same as in Linux.



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

[jira] [Commented] (HADOOP-10433) Key Management Server based on KeyProvider API

2014-04-27 Thread Hadoop QA (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982273#comment-13982273
]

Hadoop QA commented on HADOOP-10433:

{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12642105/HADOOP-10433.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 5 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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-assemblies hadoop-common-project/hadoop-common
hadoop-common-project/hadoop-kms hadoop-dist hadoop-hdfs-project/hadoop-hdfs
hadoop-hdfs-project/hadoop-hdfs-httpfs
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-mapreduce-project/hadoop-mapreduce-examples
hadoop-tools/hadoop-openstack
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:

org.apache.hadoop.crypto.key.kms.server.TestKMSServer
org.apache.hadoop.mapreduce.lib.db.TestDBJob

org.apache.hadoop.hdfs.tools.offlineEditsViewer.TestOfflineEditsViewer

The following test timeouts occurred in
hadoop-assemblies hadoop-common-project/hadoop-common
hadoop-common-project/hadoop-kms hadoop-dist hadoop-hdfs-project/hadoop-hdfs
hadoop-hdfs-project/hadoop-hdfs-httpfs
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-mapreduce-project/hadoop-mapreduce-examples
hadoop-tools/hadoop-openstack
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:

org.apache.hadoop.mapred.pipes.TestPipeApplication

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

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

This message is automatically generated.

Key Management Server based on KeyProvider API
--

Key: HADOOP-10433
URL: https://issues.apache.org/jira/browse/HADOOP-10433
Project: Hadoop Common
Issue Type: Improvement
Components: security
Affects Versions: 3.0.0
Reporter: Alejandro Abdelnur
Assignee: Alejandro Abdelnur
Attachments: HADOOP-10433.patch, HADOOP-10433.patch,
HADOOP-10433.patch, HADOOP-10433.patch, HADOOP-10433.patch,
HadoopKMSDocsv2.pdf, KMS-doc.pdf

(from HDFS-6134 proposal)
Hadoop KMS is the gateway, for Hadoop and Hadoop clients, to the underlying
KMS. It provides an interface that works with existing Hadoop security
components (authenticatication, confidentiality).
Hadoop KMS will be implemented leveraging the work being done in HADOOP-10141
and HADOOP-10177.
Hadoop KMS will provide an additional implementation of the Hadoop
KeyProvider class. This implementation will be a client-server implementation.
The client-server protocol will be secure:
* Kerberos HTTP SPNEGO (authentication)
* HTTPS for transport (confidentiality and integrity)
* Hadoop ACLs (authorization)
The Hadoop KMS implementation will not provide additional ACL to access
encrypted files. For sophisticated access control requirements, HDFS ACLs
(HDFS-4685) should be used.
Basic key administration will be supported by the Hadoop KMS via the, already
available, Hadoop KeyShell command line tool
There are minor changes that must be done in Hadoop KeyProvider functionality:
The KeyProvider contract, and the existing implementations, must be
thread-safe
KeyProvider API should have an API to generate the key material internally
JavaKeyStoreProvider should use, if present, a password provided via
configuration
KeyProvider Option and Metadata should include a label (for easier
cross-referencing)
To avoid overloading the underlying KeyProvider implementation, the Hadoop
KMS will cache keys using a TTL policy.
Scalability and High Availability of the Hadoop KMS can achieved by running
multiple instances behind a VIP/Load-Balancer. For High Availability, the
underlying KeyProvider implementation used by the Hadoop KMS must be High
Available.

--
This message was

[jira] [Commented] (HADOOP-10433) Key Management Server based on KeyProvider API

2014-04-27 Thread Hadoop QA (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982282#comment-13982282
]