You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2017/08/01 00:52:00 UTC
[jira] [Updated] (HADOOP-14683) FileStatus.compareTo binary compat
issue between 2.7 and 2.8
[ https://issues.apache.org/jira/browse/HADOOP-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated HADOOP-14683:
---------------------------------
Target Version/s: 2.9.0, 3.0.0-beta1, 2.8.2 (was: 2.9.0, 2.8.2)
> 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
> Affects Versions: 2.8.0, 2.8.1
> Reporter: Sergey Shelukhin
> Assignee: Akira Ajisaka
> Priority: Blocker
> Attachments: HADOOP-14683-branch-2-01.patch, HADOOP-14683-branch-2-02.patch
>
>
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org