[
https://issues.apache.org/jira/browse/HADOOP-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558494#comment-16558494
]
Steve Loughran commented on HADOOP-15632:
-----------------------------------------
HADOOP-14507 actually reverts the change in HADOOP-14135. That is: it restores
the constructor args of 2.6-2.8. Which is why I wasn't worried about
incompatibility there, see HADOOP-14723 for that. Looks like it isn't in
branch-2 at all. If we want to reinstate the HADOOP-14135 change in trunk, we
should think about adding HADOOP-14507 to branch-2 as well.
> Address recent API incompatibilities in cloud storage
> -----------------------------------------------------
>
> Key: HADOOP-15632
> URL: https://issues.apache.org/jira/browse/HADOOP-15632
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Sean Mackrory
> Priority: Major
>
> I think these are unlikely to cause any real issues, but I had to sift
> through a lot of reports of binary incompatibility between Hadoop 2 and
> Hadoop 3 and I'd like that report to be smaller next time :)
> HADOOP-14507 removes the single-parameter constructor from 2 classes that are
> marked as @Public and @Stable APIs. Propose we restore the original
> constructors and we document that they simply don't support per-bucket
> configs.
> HADOOP-14935 changes getFileStatusInternal from protected to private. This
> differs from the proposed patch and isn't discussed in the review, so I
> assume it's just an accident.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
