You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/09/12 00:08:08 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13453472#comment-13453472 ]
Hadoop QA commented on OOZIE-986:
---------------------------------
Testing JIRA OOZIE-986
Cleaning local svn workspace
{code}
----------------------------
Patch failed to apply to head of branch
----------------------------
{code}
> 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.2.0, 3.3.0, trunk
> Environment: RHEL 6.0
> Reporter: Steven Willis
> Labels: java, options, shellscript
> Fix For: 3.3.0, 3.2.1, trunk
>
> Attachments: OOZIE-986.patch
>
> 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.
--
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