[
https://issues.apache.org/jira/browse/HDFS-14159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734533#comment-16734533
]
Wei-Chiu Chuang commented on HDFS-14159:
----------------------------------------
The compat concern in HDFS-12882 stems from the return value change in
{{DistributedFileSystem#createPathHandle}}.
>From an API compat perspective, DistributedFileSystem class is an Unstable,
>and LimitedPrivate class, so the the change is allowed even between two
>3.0.x/3.0.y maintenance releases.
>https://hadoop.apache.org/docs/r3.1.0/hadoop-project-dist/hadoop-common/InterfaceClassification.html#Unstable
The other imcompact is induced by HDFS-12681 due to the {getBlockLocations()}
call. So that's taken care of here. Sounds like we should backport the
preceding commits. [~adam.antal] what are the two commits required for
HDFS-12681 backport? HDFS-7878 and ?
> Backporting HDFS-12882 to branch-3.0: Support full open(PathHandle) contract
> in HDFS
> ------------------------------------------------------------------------------------
>
> Key: HDFS-14159
> URL: https://issues.apache.org/jira/browse/HDFS-14159
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Affects Versions: 3.0.3
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Major
> Attachments: HDFS-12882.branch-3.0.000.patch
>
>
> This task aims to backport HDFS-12882 and some connecting commits to
> branch-3.0 without introducing API incompatibilities.
> In order to be able to cleanly backport, first HDFS-7878, then HDFS-12877
> should be backported to that branch as well (both can be executed cleanly,
> and with build success).
> Also, this patch would also introduce API backward incompatibilities in
> hadoop-hdfs-client, and we should modify it to a compat change (similar as in
> HDFS-13830 fought with this problem).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
