Return-Path: 
 <dev-return-12930-apmail-falcon-dev-archive=falcon.apache.org@falcon.apache.org>
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 D4E7018A74
	for <apmail-falcon-dev-archive@minotaur.apache.org>;
 Tue, 30 Jun 2015 22:38:27 +0000 (UTC)
Received: (qmail 10804 invoked by uid 500); 30 Jun 2015 22:38:27 -0000
Delivered-To: apmail-falcon-dev-archive@falcon.apache.org
Received: (qmail 10765 invoked by uid 500); 30 Jun 2015 22:38:27 -0000
Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@falcon.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@falcon.apache.org>
List-Post: <mailto:dev@falcon.apache.org>
List-Id: <dev.falcon.apache.org>
Reply-To: dev@falcon.apache.org
Delivered-To: mailing list dev@falcon.apache.org
Received: (qmail 10754 invoked by uid 99); 30 Jun 2015 22:38:27 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2015 22:38:27 +0000
X-ASF-Spam-Status: No, hits=-2000.7 required=5.0
	tests=ALL_TRUSTED,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; Tue, 30 Jun 2015 22:36:17 +0000
Received: (qmail 10450 invoked by uid 99); 30 Jun 2015 22:38:04 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2015 22:38:04 +0000
Date: Tue, 30 Jun 2015 22:38:04 +0000 (UTC)
From: "Janarthanan (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12841829.1435703837000.64404.1435703884552@Atlassian.JIRA>
In-Reply-To: <JIRA.12841829.1435703837000@Atlassian.JIRA>
References: <JIRA.12841829.1435703837000@Atlassian.JIRA>
 <JIRA.12841829.1435703837620@arcas>
Subject: [jira] [Created] (FALCON-1304) Falcon - Does oozie required to be
 installed explicitly?
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

Janarthanan created FALCON-1304:
-----------------------------------

             Summary: Falcon - Does oozie required to be installed explicitly?
                 Key: FALCON-1304
                 URL: https://issues.apache.org/jira/browse/FALCON-1304
             Project: Falcon
          Issue Type: Bug
            Reporter: Janarthanan
            Priority: Critical


1. Does oozie need to be installed explicitly, before starting falcon server ?

I do see an oozie package within the falcon target folder as below. What's the significance for the oozie folder within the falcon ? 

      ~/falcon-sources-0.6.1/target/falcon-0.6.1/oozie

In cluster-standalone.xml file, I see the below line which refers to oozie url. 
Do the oozie scheduler part of falcon, is listening to the port 11000 as mentioned in the examples ? 

 <interface type="workflow" endpoint="http://localhost:11000/oozie/" version="4.0.0"/>

Or, should I separately, install oozie and provide the URL in cluster definition ?

2. Does the oozie package mentioned in Installation_steps.txt is required ? Why do we need to package the oozie with the project ? Which project is referred here ? I tried packaging the falcon folder and I end up deleting the /target folder got created within the falcon source folder after building it in embedded mode. 



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