[
https://issues.apache.org/jira/browse/OOZIE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717348#comment-14717348
]
Hadoop QA commented on OOZIE-2343:
----------------------------------
Testing JIRA OOZIE-2343
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/2517/
> Shell Action should take Oozie Action config and setup HADOOP_CONF_DIR
> ----------------------------------------------------------------------
>
> Key: OOZIE-2343
> URL: https://issues.apache.org/jira/browse/OOZIE-2343
> Project: Oozie
> Issue Type: Improvement
> Components: action
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: OOZIE-2343.001.patch
>
>
> Despite being not recommended, many users still run Hadoop ecosystem programs
> from the Shell Action (e.g. hive, beeline, sqoop, etc), even though we have
> Actions for those. One of the common problems we've been seeing here lately
> is that {{HADOOP_CONF_DIR}} is inherited from the NM, and is pointing to the
> NM's copy of the Hadoop *-site.xml files, which is often not well suited for
> client programs. This can lead to all kinds of weird problems, such as
> permissions errors, missing logs, etc.
> As a workaround, we've been telling users to set {{HADOOP_CONF_DIR}} to
> {{/etc/hadoop/conf}}, however, this has some disadvantages. Ideally, these
> client programs should pick up {{OOZIE_ACTION_CONF_XML}} instead. Given that
> {{OOZIE_ACTION_CONF_XML}} is an amalgamation of all of the Hadoop *-site.xml
> plus things Oozie and the user set, we can simply have the Shell Action
> copy-paste it to the correctly named *-site.xml files, and point
> {{HADOOP_CONF_DIR}} to there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
