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 "Andrew Wang (JIRA)" <ji...@apache.org> on 2017/11/14 19:26:00 UTC
[jira] [Updated] (HDFS-12654) APPEND API call is different in
HTTPFS and NameNode REST
[ https://issues.apache.org/jira/browse/HDFS-12654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated HDFS-12654:
-------------------------------
Target Version/s: 3.0.0, 2.9.1, 2.8.4 (was: 2.6.0, 2.7.0, 2.8.0, 3.0.0)
> APPEND API call is different in HTTPFS and NameNode REST
> --------------------------------------------------------
>
> Key: HDFS-12654
> URL: https://issues.apache.org/jira/browse/HDFS-12654
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs, httpfs, namenode
> Affects Versions: 2.6.0, 2.7.0, 2.8.0, 3.0.0-beta1
> Reporter: Andras Czesznak
>
> The APPEND REST API call behaves differently in the NameNode REST and the HTTPFS codes. The NameNode version creates the target file the new data being appended to if it does not exist at the time of the call issued. The HTTPFS version assumes the target file exists when APPEND is called and can append only the new data but does not create the target file it doesn't exist.
> The two implementations should be standardized, preferably the HTTPFS version should be modified to execute an implicit CREATE if the target file does not exist.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org