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-1977) Move falcon-main hadoop version to match falcon-unit and falcon-regression hadoop versions
Date Sun, 22 May 2016 02:51:12 GMT

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

Venkat Ranganathan updated FALCON-1977:
---------------------------------------
    Summary: Move falcon-main hadoop version to match falcon-unit and falcon-regression hadoop
versions  (was: Move falcon-unit to addons as it requires a higher hadoop version)

> Move falcon-main hadoop version to match falcon-unit and falcon-regression hadoop versions
> ------------------------------------------------------------------------------------------
>
>                 Key: FALCON-1977
>                 URL: https://issues.apache.org/jira/browse/FALCON-1977
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Venkat Ranganathan
>            Assignee: Venkat Ranganathan
>
> Falcon-unit requires Hadoop 2.7.x APIs.   This is different from the falcon main which
uses 2.6.2 -  There were some discussions on keeping falcon version to 2.6.2
> As part of cleaning up hadoop-2 profile, it would be good to move falcon-unit to addons
like hivedr, hdfs-snapshot-mirroring etc which require higher versions of components and enabled
with a specific profile.   That way, users can build Falcon after explicitly updating the
component versions.
> But given that Falcon unit (an integration test) and falcon regression both require higher
version of Hadoop, it might be good to think about moving Falcon base to also default to Hadoop
2.7.1.  Will create a separate JIRA for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message