[
https://issues.apache.org/jira/browse/HDFS-14595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882517#comment-16882517
]
Wei-Chiu Chuang commented on HDFS-14595:
----------------------------------------
Thanks [~smeng].
bq. Shall we file a separate jira for updating the release doc?
No we don't need a separate jira. Just update the release doc in this jira.
Would you also take care of the checksty warning? Specifically, is it necessary
to deprecate {{getUnderConstructionFiles()}}? (Sorry i don't have a java editor
with me)
> HDFS-11848 breaks API compatibility
> -----------------------------------
>
> Key: HDFS-14595
> URL: https://issues.apache.org/jira/browse/HDFS-14595
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.2.0, 3.1.2
> Reporter: Wei-Chiu Chuang
> Assignee: Siyao Meng
> Priority: Blocker
> Attachments: HDFS-14595.001.patch, hadoop_
> 36e1870eab904d5a6f12ecfb1fdb52ca08d95ac5 to
> b241194d56f97ee372cbec7062bcf155bc3df662 compatibility report.htm
>
>
> Our internal tool caught an API compatibility issue with HDFS-11848.
> HDFS-11848 adds an additional parameter to
> DistributedFileSystem.listOpenFiles(), but it doesn't keep the existing API.
> This can cause issue when upgrading from Hadoop 2.9.0/2.8.3/3.0.0 to
> 3.0.1/3.1.0 and above.
> Suggest:
> (1) Add back the old API (which was added in HDFS-10480), and mark it
> deprecated.
> (2) Update release doc to enforce running API compatibility check for each
> releases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
