You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2017/01/06 21:50:59 UTC

[jira] [Commented] (OOZIE-2528) Print out environment variables in LauncherMapper

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

Robert Kanter commented on OOZIE-2528:
--------------------------------------

That's even before my time :)

I'm not sure, but I don't think the log4j stuff would have worked in Hadoop 1, or would have required Oozie to add those dependencies, so they just used System.out, but I don't really know.

Anyway, I agree.  It would be nice if we could use log4j and have different log levels.

> Print out environment variables in LauncherMapper
> -------------------------------------------------
>
>                 Key: OOZIE-2528
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2528
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Peter Cseh
>            Assignee: Peter Cseh
>         Attachments: OOZIE-2528-001.patch
>
>
> LauncherMapper prints out the Java properties and the parameters. It would be nice to print environment variables as well as it could help troubleshooting.



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