Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 13 Mar 2015 23:09:38 +0000 (UTC)
From: "Colin Patrick McCabe (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12777378.1424826480000.91363.1426288178716@Atlassian.JIRA>
In-Reply-To: <JIRA.12777378.1424826480000@Atlassian.JIRA>
References: <JIRA.12777378.1424826480000@Atlassian.JIRA>
 <JIRA.12777378.1424826480489@arcas>
Subject: [jira] [Commented] (HDFS-7838) Expose truncate API for libhdfs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361279#comment-14361279 ] 

Colin Patrick McCabe commented on HDFS-7838:
--------------------------------------------

The libhdfs part looks correct, but you didn't add a stub function to libwebhdfs which returns {{ENOTSUP}} like I asked.

I understand that you are planning on adding full support in libwebhdfs in a follow-on jira, but it would be better to have the function introduced there in this JIRA, so that people would not get linker failures when trying to link a binary using {{hdfsTruncate}} against {{libwebhdfs}}.  {{libwebhdfs}} must implement every function in {{hdfs.h}}.

> Expose truncate API for libhdfs
> -------------------------------
>
>                 Key: HDFS-7838
>                 URL: https://issues.apache.org/jira/browse/HDFS-7838
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>    Affects Versions: 2.7.0
>            Reporter: Yi Liu
>            Assignee: Yi Liu
>         Attachments: HDFS-7838.001.patch, HDFS-7838.002.patch, HDFS-7838.003.patch
>
>
> It's good to expose truncate in libhdfs.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)