You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Pragya Mittal (JIRA)" <ji...@apache.org> on 2015/08/04 13:24:05 UTC
[jira] [Commented] (FALCON-1304) Falcon - Does oozie required to be
installed explicitly?
[ https://issues.apache.org/jira/browse/FALCON-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653470#comment-14653470 ]
Pragya Mittal commented on FALCON-1304:
---------------------------------------
Fixed in FALCON-1301
> 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)