[
https://issues.apache.org/jira/browse/FALCON-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296650#comment-15296650
]
Venkat Ranganathan commented on FALCON-1977:
--------------------------------------------
Spoke with [~sriksun] offline. For the current 0.10 release we will keep the
2.6.2 for main/2.7.1 for unit so that people using 2.6.x clusters can still
install falcon 0.10 without worries of feature creep from 2.7.x into the core
codebase. Will keep this ticket open for a future release
> 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)
