[
https://issues.apache.org/jira/browse/HDFS-14159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724013#comment-16724013
]
Adam Antal commented on HDFS-14159:
-----------------------------------
Some additional notes from my side:
* Cherry-picking HDFS-12882 from trunk would cause some conflicts, lots of
which is trivial, and one is because HDFS-13136 is already in branch-3.0.
* Build fails because of missing HDFS-12681: a call in {{DFSClient.java}} must
be changed to {{getBlockLocations()}}.
** Note: backporting HDFS-12681 too would introduce further breaking API
changes.
* Since it would be a minor version change in branch-3.0, my suggestion would
be to modify that API, using the old interface. (the same as in HDFS-13830).
** In HDFS-13830 they detected that function name has been changed in
HDFS-12681, so they kept the old function name {{flags()}} but added the new
param - I think we should do that exact same here.
> 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
>
> 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]
