Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DB066200AC5 for ; Sun, 22 May 2016 02:43:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D9C6F160A04; Sun, 22 May 2016 00:43:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2CFB6160A27 for ; Sun, 22 May 2016 02:43:17 +0200 (CEST) Received: (qmail 91969 invoked by uid 500); 22 May 2016 00:43:16 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 91958 invoked by uid 99); 22 May 2016 00:43:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 May 2016 00:43:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id ECB201A0146 for ; Sun, 22 May 2016 00:43:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.221 X-Spam-Level: X-Spam-Status: No, score=-3.221 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id z_kvcv7F6Br3 for ; Sun, 22 May 2016 00:43:15 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 537945F46F for ; Sun, 22 May 2016 00:43:14 +0000 (UTC) Received: (qmail 91631 invoked by uid 99); 22 May 2016 00:43:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 May 2016 00:43:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 042932C1F58 for ; Sun, 22 May 2016 00:43:13 +0000 (UTC) Date: Sun, 22 May 2016 00:43:13 +0000 (UTC) From: "Venkat Ranganathan (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (FALCON-1977) Move falcon-unit to addons as it requires a higher hadoop version MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 22 May 2016 00:43:18 -0000 [ https://issues.apache.org/jira/browse/FALCON-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan reassigned FALCON-1977: ------------------------------------------ Assignee: Venkat Ranganathan > Move falcon-unit to addons as it requires a higher hadoop version > ----------------------------------------------------------------- > > Key: FALCON-1977 > URL: https://issues.apache.org/jira/browse/FALCON-1977 > Project: Falcon > Issue Type: Sub-task > 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)