[
https://issues.apache.org/jira/browse/HDFS-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302310#comment-14302310
]
Anu Engineer commented on HDFS-7520:
------------------------------------
This patch defines HADOOP_OPENSSL_LIBRARY if and only if we find a
USABLE_OPENSSL. Based on Chris analysis, it is possible for us to find a
invalid OpenSSL installation but still have _buildSupportsOpenssl() function
return true, since the HADOOP_OPENSSL_LIBRARY gets defined in CMake file.
> checknative should display a nicer error message when openssl support is not
> compiled in
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-7520
> URL: https://issues.apache.org/jira/browse/HDFS-7520
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Colin Patrick McCabe
> Assignee: Anu Engineer
>
> checknative should display a nicer error message when openssl support is not
> compiled in. Currently, it displays this:
> {code}
> [cmccabe@keter hadoop]$ hadoop checknative
> 14/12/12 14:08:43 INFO bzip2.Bzip2Factory: Successfully loaded & initialized
> native-bzip2 library system-native
> 14/12/12 14:08:43 INFO zlib.ZlibFactory: Successfully loaded & initialized
> native-zlib library
> Native library checking:
> hadoop: true /usr/lib/hadoop/lib/native/libhadoop.so.1.0.0
> zlib: true /lib64/libz.so.1
> snappy: true /usr/lib64/libsnappy.so.1
> lz4: true revision:99
> bzip2: true /lib64/libbz2.so.1
> openssl: false org.apache.hadoop.crypto.OpensslCipher.initIDs()V
> {code}
> Instead, we should display something like this, if openssl is not supported
> by the current build:
> {code}
> openssl: false Hadoop was built without openssl support.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)