Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 030CF179AC for ; Thu, 2 Apr 2015 13:29:36 +0000 (UTC) Received: (qmail 69175 invoked by uid 500); 2 Apr 2015 13:28:57 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 69138 invoked by uid 500); 2 Apr 2015 13:28:57 -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 69058 invoked by uid 99); 2 Apr 2015 13:28:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2015 13:28:57 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 02 Apr 2015 13:28:56 +0000 Received: (qmail 53431 invoked by uid 99); 2 Apr 2015 13:28:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2015 13:28:36 +0000 Date: Thu, 2 Apr 2015 13:28:36 +0000 (UTC) From: "Pallavi Rao (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1133) Adding Falcon Unit MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/FALCON-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392485#comment-14392485 ] Pallavi Rao commented on FALCON-1133: ------------------------------------- +1 Once we have a separate Falcon Unit package, that can be reused for our Integration Tests too. > Adding Falcon Unit > ------------------- > > Key: FALCON-1133 > URL: https://issues.apache.org/jira/browse/FALCON-1133 > Project: Falcon > Issue Type: New Feature > Reporter: karan kumar > Assignee: karan kumar > > As falcon has a bunch of handcrafted xmls ,this results in manual errors such as typos, giving bad arguments, xml errors etc while deploying a new job. > For validating the xmls as well as checking the job is getting the correct set of configs, a mock run is needed in a full fledged setup of falcon/hadoop/oozie. This I feel is a overkill. > I propose that we start work on falcon unit which will intialize falcon/hadoop/oozie in local mode and run the job locally to test the configs and also can be extended to validate input and output datesets. This will really help in easily onboarding to falcon jobs as in a matter of minutes u can test your process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)