hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18903) Investigate PreCommit miss on Hadoop-3 compatibility
Date Thu, 28 Sep 2017 19:15:03 GMT

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

Josh Elser commented on HBASE-18903:
------------------------------------

Best as I can tell, this is just a defect with master, not branch-2.

> 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)

Mime
View raw message