You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Pierre de Freminville (JIRA)" <ji...@apache.org> on 2016/11/25 18:12:59 UTC
[jira] [Updated] (HAWQ-1173) hdfsConnect in libhdfs3 is not
consistent with hdfsConnect in native libhdfs (JNI) when port is 0
[ https://issues.apache.org/jira/browse/HAWQ-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre de Freminville updated HAWQ-1173:
----------------------------------------
Priority: Minor (was: Trivial)
> hdfsConnect in libhdfs3 is not consistent with hdfsConnect in native libhdfs (JNI) when port is 0
> -------------------------------------------------------------------------------------------------
>
> Key: HAWQ-1173
> URL: https://issues.apache.org/jira/browse/HAWQ-1173
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: libhdfs
> Reporter: Pierre de Freminville
> Assignee: Lei Chang
> Priority: Minor
>
> Hello,
> I noticed that the following is not possible with libhdfs3
> {code}hdfsFS fs = hdfsConnect("default", 0);{code}
> because of asserts such as:
> {code}PARAMETER_ASSERT(port > 0, NULL, EINVAL);{code}
> I could be nice to allow that to be consistent with what is done in the native libhdfs (JNI).
> The file of interest in the native library is:
> * hadoop-hdfs-native-client/src/main/native/libhdfs/hdfs.c
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)