[
https://issues.apache.org/jira/browse/HDFS-14159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736847#comment-16736847
]
Adam Antal commented on HDFS-14159:
-----------------------------------
Hi [~virajith], HDFS-7878 and HDFS-12877 are clean cherry-pick from trunk to
branch-3.0. Also I did some internal testing, and the tests pass. So I thought
I did not need to add them as well, since they just need to be cherry-picked
without any further modification. This issue only concerns HDFS-12882, as it is
not a clean cherry-pick, and has some problems that need to be addressed.
So in case of HDFS-7878 and HDFS-12877 a committer can cherry-pick those to
branch-3.0 from trunk without modification. If you think branch-3.0 patches to
those issues are important, than I can upload those to HDFS-7878 and HDFS-12877.
> 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]