falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saktheesh Balaraj (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FALCON-1618) Unable to run OOZIE (MapReduce) workflow through Falcon Process
Date Mon, 30 Nov 2015 13:32:10 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029691#comment-15029691
] 

Saktheesh Balaraj edited comment on FALCON-1618 at 11/30/15 1:31 PM:
---------------------------------------------------------------------

1. In the real Cluster we have used blue print. Could you please point me the right doc for
the properties need to be added in oozie-site?
2. In Sanbox 2.3.2, the same issue persist. I had to add these properties manually. This was
not the case with 2.3.1


was (Author: saktheesh):
1. In the real Cluster we have used blue print. Could you please point me the right doc for
the properties need to be added in oozie-site?
2. In Sanbox 2.3.1, the same issue persist. I had to add these properties manually. This was
not the case with 2.3.1

> Unable to run OOZIE (MapReduce)  workflow through Falcon Process
> ----------------------------------------------------------------
>
>                 Key: FALCON-1618
>                 URL: https://issues.apache.org/jira/browse/FALCON-1618
>             Project: Falcon
>          Issue Type: Bug
>          Components: oozie
>    Affects Versions: 0.6.1, trunk
>         Environment: HDP 2.3.2
>            Reporter: Saktheesh Balaraj
>            Assignee: Peeyush Bishnoi
>            Priority: Blocker
>         Attachments: SampleProcess.xml, Simplefeedin.xml, Simplefeedout.xml, workflow.xml
>
>
> Error:
> ~~~~
> Caused by: org.apache.falcon.FalconException: E1004 : E1004: Expression language evaluation
error, Unable to evaluate :${dataIn('input', 'null')}:
>         at org.apache.falcon.workflow.engine.OozieWorkflowEngine.dryRunInternal(OozieWorkflowEngine.java:234)
> Environment:  HDP2.3.2 Sandbox
> ~~~~~~~~~~
> Observation:
> ~~~~~~~~~~
> This could be due to wrong property values in OOZIE coordinator file being generated
by Falcon for an OOZIE workflow (MR).
> Current Values:
>                 <property>
>                     <name>falconInPaths</name>
>                     <value>${dataIn('input', 'null')}</value>
>                 </property>
>                 <property>
>                     <name>input</name>
>                     <value>${dataIn('input', 'null')}</value>
>                 </property>
> Expected Values:
> ~~~~~~~~~~~~~
> <property>
>                     <name>falconInPaths</name>
>                     <value>coord:{dataIn('input', 'null')}</value>
>                 </property>
>                 <property>
>                     <name>input</name>
>                     <value>coord:{dataIn('input', 'null')}</value>
>                 </property>
> Steps to simulate the problem:
> ~~~~~~~~~~~~~~~~~~~~~~~~
> 1.Install  HDP 2.3.2 Sandbox
> 	2. Enable Falcon through Ambari
> 	3. Configure Feed (input), Feed (output)
> 	4. Configure process with the following configurations
> 		-input (input Feed)
> 		-output (output Feed)
> 	5. Schedule the process through Falcon 



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

Mime
View raw message