[ https://issues.apache.org/jira/browse/HDFS-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430419#comment-13430419 ]
Hadoop QA commented on HDFS-3637: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12539666/HDFS-3637.patch against trunk revision . -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2963//console This message is automatically generated. > Add support for encrypting the DataTransferProtocol > --------------------------------------------------- > > Key: HDFS-3637 > URL: https://issues.apache.org/jira/browse/HDFS-3637 > Project: Hadoop HDFS > Issue Type: New Feature > Components: data-node, hdfs client, security > Affects Versions: 2.0.0-alpha > Reporter: Aaron T. Myers > Assignee: Aaron T. Myers > Fix For: 2.2.0-alpha > > Attachments: HDFS-3637.patch, HDFS-3637.patch, HDFS-3637.patch, > HDFS-3637.patch, HDFS-3637.patch > > > Currently all HDFS RPCs performed by NNs/DNs/clients can be optionally > encrypted. However, actual data read or written between DNs and clients (or > DNs to DNs) is sent in the clear. When processing sensitive data on a shared > cluster, confidentiality of the data read/written from/to HDFS may be desired. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira