You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Steven Willis (JIRA)" <ji...@apache.org> on 2012/09/11 22:20:08 UTC

[jira] [Updated] (OOZIE-986) Oozie client shell script should use consistent naming for java options

     [ https://issues.apache.org/jira/browse/OOZIE-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Willis updated OOZIE-986:
--------------------------------

    Summary: Oozie client shell script should use consistent naming for java options  (was: Oozie shell script should allow for setting of java options)
    
> Oozie client shell script should use consistent naming for java options
> -----------------------------------------------------------------------
>
>                 Key: OOZIE-986
>                 URL: https://issues.apache.org/jira/browse/OOZIE-986
>             Project: Oozie
>          Issue Type: Improvement
>          Components: scripts
>    Affects Versions: 3.1.3, 3.2.0
>         Environment: RHEL 6.0
>            Reporter: Steven Willis
>              Labels: java, options, shellscript
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> All the hadoop shell scripts (hadoop, hdfs, mapred, yarn) allow the setting of HADOOP_CLIENT_OPTS to pass custom options to java. I think the oozie shell script should allow the same through OOZIE_CLIENT_OPTS and similarly respect JAVA_HEAP_MAX like the hadoop shell scripts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira