falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1976) Remove hadoop-2 profile
Date Sun, 22 May 2016 00:50:12 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295343#comment-15295343

ASF GitHub Bot commented on FALCON-1976:

GitHub user vrangan opened a pull request:


    FALCON-1976 and FALCON-1977:  Remove hadoop-2 profile and move unit t…

    Removed hadoop-2 profile and moved falcon-unit to addons

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vrangan/falcon FALCON-1976

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #156
commit 55c21b4cbd0c5e1595b358a54a6350437812226c
Author: Venkat Ranganathan <venkat@hortonworks.com>
Date:   2016-05-22T00:48:14Z

    FALCON-1976 and FALCON-1977:  Remove hadoop-2 profile and move unit to addons


> Remove hadoop-2 profile
> -----------------------
>                 Key: FALCON-1976
>                 URL: https://issues.apache.org/jira/browse/FALCON-1976
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Venkat Ranganathan
>            Assignee: Venkat Ranganathan
> I have been debugging the hbase backend issue and with maven 3.3.9 everything works fine,
but it looks like
>    * jenkins pre-commit is using 3.2.x
>    * Some of the RE folks I talked to say there are still using 3.1.1
> So, after a few experiments, I see that dependency management within a profile works
very well only in 3.3.9 (test classpath gets messed up in various ways in 3.2.x version of
maven for some reason.   changing surefire plugin version does not help either).  Patching
this in child poms is either hacky or  not elegant.
> So,  removing hadoop-2 profile as we no longer support hadoop-1 and this resolves many
of the 3.2.5 issues
> Also saw that falcon-unit is having its own version of hadoop version (2.7.1) instead
of using the parent pom version.   This might be the cause of some intermittent issues people
were reporting.   I will create a JIRA to move falcon-unit to addons just like hivedr, hdfs-snapshot-mirroring
etc that require higher component versions

This message was sent by Atlassian JIRA

View raw message