Masatake Iwasaki resolved HDFS-12654.
    Resolution: Not A Problem

I'm closing this as not-a-problem. Please reopen if you can reproduce the 500 
issue. We should update title on reopen. Thanks for pinging me, [~Sammi].

> 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
>            Priority: Major
> 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

To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to