[
https://issues.apache.org/jira/browse/OOZIE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Salamon updated OOZIE-2738:
----------------------------------
Priority: Major (was: Critical)
> Output of SSH action should be avaialbe in logs by default + allow capture it
> raw (no properties file)
> ------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-2738
> URL: https://issues.apache.org/jira/browse/OOZIE-2738
> Project: Oozie
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 4.2.0
> Reporter: Raphael Jolivet
> Priority: Major
>
> From, the docs, I understand that capturing output of a remote SSH script
> requires :
> * Explicit <capture-output/> tag
> * Ensuring the output to be a java properties file, even in case of error.
> I find this behavior quite limiting and counter intuitive.
> I would expect that, by default, the complete output of any script call would
> be available in some log file, for troubleshooting.
> Also, I would expect to have some <capture-raw-output/> tag, in order to
> forward the output of a failing script to an email for instance.
> Instead of that, we need to adapt existing scripts, in order to output
> meaningful error in the very restrictive format :
> '"error=Some short error"
> This is not always possible, as it is hard to control the output of the
> underlying commands called by a script (bash typically).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
