[
https://issues.apache.org/jira/browse/HDFS-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Lamb updated HDFS-6954:
-------------------------------
Attachment: HDFS-6954.003.patch
[~andrew.wang],
Good idea. I've reverted those back to {} style formatting. I had changed them
originally because warn doesn't have that style.
I'm not sure what the rash of unit test failures is about. While it looks
related, it also looks like a possible jenkins patch application/compilation
failure. In any case, I ran a handful of the failed unit tests on my local
machine and they passed. So perhaps it was spurious. We can see on the next
jenkins run.
> With crypto, no native lib systems are too verbose
> --------------------------------------------------
>
> Key: HDFS-6954
> URL: https://issues.apache.org/jira/browse/HDFS-6954
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: encryption
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Charles Lamb
> Attachments: HDFS-6954.001.patch, HDFS-6954.002.patch,
> HDFS-6954.003.patch
>
>
> Running commands on a machine without a native library results in:
> {code}
> $ bin/hdfs dfs -put /etc/hosts /tmp
> 14/08/27 07:16:10 WARN util.NativeCodeLoader: Unable to load native-hadoop
> library for your platform... using builtin-java classes where applicable
> 14/08/27 07:16:11 WARN crypto.CryptoCodec: Crypto codec
> org.apache.hadoop.crypto.OpensslAesCtrCryptoCodec is not available.
> 14/08/27 07:16:11 INFO hdfs.DFSClient: No KeyProvider found.
> {code}
> This is way too much.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
