OOZIE-1283 Remove the old ssh documentation (Jan Hentschel via rkanter)
Project: http://git-wip-us.apache.org/repos/asf/oozie/repo Commit: http://git-wip-us.apache.org/repos/asf/oozie/commit/f110c33b Tree: http://git-wip-us.apache.org/repos/asf/oozie/tree/f110c33b Diff: http://git-wip-us.apache.org/repos/asf/oozie/diff/f110c33b Branch: refs/heads/oya Commit: f110c33b221ed14ef68bf20298d2933b56186844 Parents: 6bac847 Author: Robert Kanter <rkan...@apache.org> Authored: Tue Apr 4 14:44:29 2017 -0700 Committer: Robert Kanter <rkan...@apache.org> Committed: Tue Apr 4 14:44:29 2017 -0700 ---------------------------------------------------------------------- .../src/site/twiki/WorkflowFunctionalSpec.twiki | 85 +------------------- release-log.txt | 1 + 2 files changed, 4 insertions(+), 82 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/oozie/blob/f110c33b/docs/src/site/twiki/WorkflowFunctionalSpec.twiki ---------------------------------------------------------------------- diff --git a/docs/src/site/twiki/WorkflowFunctionalSpec.twiki b/docs/src/site/twiki/WorkflowFunctionalSpec.twiki index 460f6e5..fa6a84c 100644 --- a/docs/src/site/twiki/WorkflowFunctionalSpec.twiki +++ b/docs/src/site/twiki/WorkflowFunctionalSpec.twiki @@ -1276,87 +1276,8 @@ by any =job-xml= elements. </workflow-app> </verbatim> -#SshAction ----++++ 3.2.5 Ssh Action - -*NOTE: SSH actions are deprecated in Oozie schema 0.1, and removed in Oozie schema 0.2* - -The =ssh= action starts a shell command on a remote machine as a remote secure shell in background. The workflow job -will wait until the remote shell command completes before continuing to the next action. - -The shell command must be present in the remote machine and it must be available for execution via the command path. - -The shell command is executed in the home directory of the specified user in the remote host. - -The output (STDOUT) of the ssh job can be made available to the workflow job after the ssh job ends. This information -could be used from within decision nodes. If the output of the ssh job is made available to the workflow job the shell -command must follow the following requirements: - - * The format of the output must be a valid Java Properties file. - * The size of the output must not exceed 2KB. - -*Syntax:* - -<verbatim> -<workflow-app name="[WF-DEF-NAME]" xmlns="uri:oozie:workflow:0.1"> - ... - <action name="[NODE-NAME]"> - <ssh> - <host>[USER]@[HOST]</host> - <command>[SHELL]</command> - <args>[ARGUMENTS]</args> - ... - <capture-output/> - </ssh> - <ok to="[NODE-NAME]"/> - <error to="[NODE-NAME]"/> - </action> - ... -</workflow-app> -</verbatim> - -The =host= indicates the user and host where the shell will be executed. - -The =command= element indicates the shell command to execute. - -The =args= element, if present, contains parameters to be passed to the shell command. If more than one =args= element -is present they are concatenated in order. - -If the =capture-output= element is present, it indicates Oozie to capture output of the STDOUT of the ssh command -execution. The ssh command output must be in Java Properties file format and it must not exceed 2KB. From within the -workflow definition, the output of an ssh action node is accessible via the =String action:output(String node, -String key)= function (Refer to section '4.2.6 Action EL Functions'). - -The configuration of the =ssh= action can be parameterized (templatized) using EL expressions. - -*Example:* - -<verbatim> -<workflow-app name="sample-wf" xmlns="uri:oozie:workflow:0.1"> - ... - <action name="myssjob"> - <ssh> - <host>f...@bar.com<host> - <command>uploaddata</command> - <args>jdbc:derby://bar.com:1527/myDB</args> - <args>hdfs://foobar.com:8020/usr/tucu/myData</args> - </ssh> - <ok to="myotherjob"/> - <error to="errorcleanup"/> - </action> - ... -</workflow-app> -</verbatim> - -In the above example, the =uploaddata= shell command is executed with two arguments, =jdbc:derby://foo.com:1527/myDB= -and =hdfs://foobar.com:8020/usr/tucu/myData=. - -The =uploaddata= shell must be available in the remote host and available in the command path. - -The output of the command will be ignored because the =capture-output= element is not present. - #SubWorkflowAction ----++++ 3.2.6 Sub-workflow Action +---++++ 3.2.5 Sub-workflow Action The =sub-workflow= action runs a child workflow job, the child workflow job can be in the same Oozie system or in another Oozie system. @@ -1437,7 +1358,7 @@ in oozie-site.xml to set the maximum depth of subworkflow calls. For example, i can start subwf2, which can start subwf3; but if subwf3 tries to start subwf4, then the action will fail. The default is 50. #JavaAction ----++++ 3.2.7 Java Action +---++++ 3.2.6 Java Action The =java= action will execute the =public static void main(String[] args)= method of the specified main Java class. @@ -1605,7 +1526,7 @@ All the above elements can be parameterized (templatized) using EL expressions. </workflow-app> </verbatim> ----+++++ 3.2.7.1 Overriding an action's Main class +---+++++ 3.2.6.1 Overriding an action's Main class This feature is useful for developers to change the Main classes without having to recompile or redeploy Oozie. http://git-wip-us.apache.org/repos/asf/oozie/blob/f110c33b/release-log.txt ---------------------------------------------------------------------- diff --git a/release-log.txt b/release-log.txt index 89405a5..faa30b7 100644 --- a/release-log.txt +++ b/release-log.txt @@ -1,5 +1,6 @@ -- Oozie 4.4.0 release (trunk - unreleased) +OOZIE-1283 Remove the old ssh documentation (Jan Hentschel via rkanter) OOZIE-2845 Replace reflection-based code which sets variable in HiveConf (pbacsko via abhishekbafna) OOZIE-2831 Update maven-project-info-reports-plugin to 2.9 (asasvari via gezapeti) OOZIE-2753 Update Docs for Jetty Tomcat changes (asasvari via abhishekbafna)
