falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkat Ranganathan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1976) Remove hadoop-2 profile
Date Sun, 22 May 2016 00:43:13 GMT

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

Venkat Ranganathan updated FALCON-1976:
---------------------------------------
    Issue Type: Bug  (was: Sub-task)
        Parent:     (was: FALCON-1858)

> 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
(v6.3.4#6332)

Mime
View raw message