phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4408) Figure out Hadoop version compatibility
Date Tue, 12 Dec 2017 00:36:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286856#comment-16286856
] 

Josh Elser commented on PHOENIX-4408:
-------------------------------------

Thanks, [~karanmehta93]!

The other wrinkle we have is dealing with the phoenix-hive integration. If we want to support
the latest Hive (3.0), we'll have a really hard time on our hands keeping Hive 1 and compatibility
too. Last I checked, Hive 3.0 dropped support for everything prior to Hadoop 3.0 which is
why I mention it here too. If Hive is playing hardball, we get forced into doing the same.

> Figure out Hadoop version compatibility
> ---------------------------------------
>
>                 Key: PHOENIX-4408
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4408
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>            Priority: Blocker
>             Fix For: 5.0.0
>
>
> The 5.x-HBase-2.0 branch is presently incompatible with both Hadoop 2.7 and Hadoop 3.0.
> This stems from PhoenixMetricsSink and LoggingSink both of which extend MetricsSink from
Hadoop. Hadoop leaks a commons-configuration class into a method signature and changes the
dependency across versions.
> This makes it extremely annoying to work around downstream (we would have to create multiple
maven modules to shim around this). We should figure out what compatibility we want to have.
 Post PHOENIX-4405, it's only Hadoop3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message