[
https://issues.apache.org/jira/browse/HADOOP-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099531#comment-16099531
]
Akira Ajisaka commented on HADOOP-14683:
----------------------------------------
It is not possible to add old overload and keep new api because of compile
error.
{noformat}
[ERROR]
/Users/ajisaka/git/hadoop/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileStatus.java:[332,14]
name clash: compareTo(org.apache.hadoop.fs.FileStatus) in
org.apache.hadoop.fs.FileStatus overrides a method whose erasure is the same as
another method, yet neither overrides the other
[ERROR] first method: compareTo(java.lang.Object) in
org.apache.hadoop.fs.FileStatus
[ERROR] second method: compareTo(T) in java.lang.Comparable
{noformat}
This API is {{@Public}} and {{@Stable}}, so I'm thinking it's good to revert
HADOOP-12209 from branch-2 and branch-2.8.
> FileStatus.compareTo binary compat issue between 2.7 and 2.8
> ------------------------------------------------------------
>
> Key: HADOOP-14683
> URL: https://issues.apache.org/jira/browse/HADOOP-14683
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Sergey Shelukhin
>
> See HIVE-17133. Looks like the signature change is causing issues; according
> to [~jnp] this is a public API.
> Is it possible to add the old overload back (keeping the new one presumably)
> in a point release on 2.8? That way we can avoid creating yet another shim
> for this in Hive.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
