falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pragya Mittal (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FALCON-1304) Falcon - Does oozie required to be installed explicitly?
Date Tue, 04 Aug 2015 11:53:04 GMT

     [ https://issues.apache.org/jira/browse/FALCON-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pragya Mittal resolved FALCON-1304.
-----------------------------------
    Resolution: Fixed

> 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
>            Assignee: Pragya Mittal
>            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)

Mime
View raw message