Repository: oozie
Updated Branches:
  refs/heads/master 69b6aa8dd -> eebff9d35


OOZIE-1236. Documentation on capture-output element for Java action has 
incorrect property to get the filename. (Meenakshi Lakshmanan via harsh)


Project: http://git-wip-us.apache.org/repos/asf/oozie/repo
Commit: http://git-wip-us.apache.org/repos/asf/oozie/commit/eebff9d3
Tree: http://git-wip-us.apache.org/repos/asf/oozie/tree/eebff9d3
Diff: http://git-wip-us.apache.org/repos/asf/oozie/diff/eebff9d3

Branch: refs/heads/master
Commit: eebff9d35f2686a2282f771d409fcf3024b078c7
Parents: 69b6aa8
Author: Harsh J <[email protected]>
Authored: Mon Feb 2 11:11:55 2015 +0530
Committer: Harsh J <[email protected]>
Committed: Mon Feb 2 11:11:55 2015 +0530

----------------------------------------------------------------------
 docs/src/site/twiki/WorkflowFunctionalSpec.twiki | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/oozie/blob/eebff9d3/docs/src/site/twiki/WorkflowFunctionalSpec.twiki
----------------------------------------------------------------------
diff --git a/docs/src/site/twiki/WorkflowFunctionalSpec.twiki 
b/docs/src/site/twiki/WorkflowFunctionalSpec.twiki
index f9ec18c..4833bce 100644
--- a/docs/src/site/twiki/WorkflowFunctionalSpec.twiki
+++ b/docs/src/site/twiki/WorkflowFunctionalSpec.twiki
@@ -1462,7 +1462,7 @@ application. Refer to section [#FilesAchives][Adding 
Files and Archives for the
 
 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=
+property specified by the constant =oozie.action.output.properties=
 
 *IMPORTANT:* In order for a Java action to succeed on a secure cluster, it 
must propagate the Hadoop delegation token like in the
 following code snippet (this is benign on non-secure clusters):

Reply via email to