You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2018/02/15 16:29:02 UTC

[jira] [Updated] (PHOENIX-4408) Figure out Hadoop version compatibility

     [ https://issues.apache.org/jira/browse/PHOENIX-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated PHOENIX-4408:
--------------------------------
    Fix Version/s:     (was: 5.0.0-alpha)
                   5.0.0

> 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
(v7.6.3#76005)