You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/03/22 21:57:05 UTC
[jira] [Commented] (HDFS-9679) libhdfs++: Fix inconsistencies with
libhdfs C API
[ https://issues.apache.org/jira/browse/HDFS-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410404#comment-16410404 ]
Hudson commented on HDFS-9679:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13869 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/13869/])
HDFS-9679: Fix inconsistencies with libhdfs C API. Contributed by James (james.clampffer: rev ad23cf14903ef544e78c9abedb0387aec2b66f0b)
* (edit) hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/bindings/c/hdfs.cc
> libhdfs++: Fix inconsistencies with libhdfs C API
> -------------------------------------------------
>
> Key: HDFS-9679
> URL: https://issues.apache.org/jira/browse/HDFS-9679
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: James Clampffer
> Assignee: James Clampffer
> Priority: Major
> Attachments: HDFS-9679.HDFS-8707.000.patch
>
>
> There is at least 1 minor inconsistency with the libhdfs api. Currently hdfsSeek returns a 32 bit int to indicate the result offset of a seek, similar to a posix lseek. It should return 1 and 0 as error codes. If someone starts using hdfsSeek like they would lseek everything works great - until you have an >4GB offset and the upper bits are truncated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org