[
https://issues.apache.org/jira/browse/HADOOP-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558636#comment-16558636
]
Steve Loughran commented on HADOOP-15632:
-----------------------------------------
w.r.t. HADOOP-14935, not sure it's really a public API, so not worth worrying
about. Though I don't see why NativeAzureFileSystem should have been tagged
Public+Stable in the first place, as only the FileSystem API should be
considered the API external code can use. Maybe downgrade to private there (I
don't see anything in the compatibility doc on that topic tho', unless
[[email protected]] has an opinion.
For HADOOP-14507, given branch-2 is still alive, I'd be happy with reinstating
the 3-arg ctor there. and the 2-arg one to trunk. That way, you get to
implement something which works in both places
> 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]
