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

Posted to issues@hbase.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2017/09/28 19:15:03 UTC

[jira] [Updated] (HBASE-18903) Investigate PreCommit miss on Hadoop-3 compatibility

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

Josh Elser updated HBASE-18903:
-------------------------------
    Fix Version/s:     (was: 2.0.0-alpha-4)
                   3.0.0

> Investigate PreCommit miss on Hadoop-3 compatibility
> ----------------------------------------------------
>
>                 Key: HBASE-18903
>                 URL: https://issues.apache.org/jira/browse/HBASE-18903
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 3.0.0
>
>
> We accidentally committed HBASE-18843 without realizing that it broke compilation against Hadoop 3. The PreCommit check reported that it was OK against Hadoop3, so we were none-the-wiser.
> Appy noticed that the reason for this was that some Hadoop 2.7.1. jars were actually being used instead of the Hadoop 3 jars.
> Need to investigate what the heck is happening to prevent further bad commits.



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