[
https://issues.apache.org/jira/browse/HDFS-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280984#comment-13280984
]
Kihwal Lee commented on HDFS-3453:
----------------------------------
The attached patch changes how namenode.create() is called. If createParent is
false (regular create), the old create() method is used. This only changes how
things are internally wired and does not introduce any incompatibility.
> HDFS does not use ClientProtocol in a backward-compatible way
> -------------------------------------------------------------
>
> Key: HDFS-3453
> URL: https://issues.apache.org/jira/browse/HDFS-3453
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 1.0.0
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Fix For: 1.1.0
>
> Attachments: hdfs-3453-branch-1.patch
>
>
> HDFS-617 was brought into branch-0.20-security/branch-1 to support
> non-recursive create, along with HADOOP-6840 and HADOOP-6886. However, the
> changes in HDFS was done in an incompatible way, making the client unusable
> against older clusters, even when plain old create() is called. This is
> because DFS now internally calls create() through the newly introduced
> method. By simply changing how the methods are wired internally, we can
> remove this limitation. We may eventually switch back to the approach in
> HDFS-617 when the majority of users adopt branch-1 based releases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
