You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2015/02/03 23:01:37 UTC
[jira] [Resolved] (OOZIE-445) OOZIE-28: Documentation on Capturing
Output is Wrong
[ https://issues.apache.org/jira/browse/OOZIE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J resolved OOZIE-445.
---------------------------
Resolution: Duplicate
> OOZIE-28: Documentation on Capturing Output is Wrong
> ----------------------------------------------------
>
> Key: OOZIE-445
> URL: https://issues.apache.org/jira/browse/OOZIE-445
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
> Assignee: Roman Shaposhnik
> Priority: Minor
>
> The [Oozie 2.3 documentation|http://yahoo.github.com/oozie/releases/2.3.0/WorkflowFunctionalSpec.html#a3.2.7_Java_Action] has this to say about capturing the output of a Java action:
> {quote}
> The capture-output element can be used to propagate values back into Oozie context, which can then be accessed via EL-functions. This needs to be written out as a java properties format file. The filename is obtained via a System property specified by the constant JavaMainMapper.OOZIE_JAVA_MAIN_CAPTURE_OUTPUT_FILE
> {quote}
> That last sentence is wrong for the latest releases. The Java action should write out the properties to a file whose name is given by the system property {{oozie.action.output.properties}}. These properties can then be accessed in a subsequent action using an EL expression like ${wf:actionData('foo')['bar']}, where {{foo}} is the name of the Java action and {{bar}} is the key for the desired property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)