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

TezQA commented on TEZ-2679:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12766254/TEZ-2679.2.patch
  against master revision 822bc69.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-TEZ-Build/1213//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1213//console

This message is automatically generated.

> Admin forms of launch env settings
> ----------------------------------
>
>                 Key: TEZ-2679
>                 URL: https://issues.apache.org/jira/browse/TEZ-2679
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Jason Lowe
>            Assignee: Jonathan Eagles
>         Attachments: TEZ-2679.1.patch, TEZ-2679.2.patch
>
>
> Tez should provide corresponding admin configs for launch env and java opt 
> settings that can be specified in tez-site.xml by cluster admins.  For 
> example, if users override the launch env settings to setup LD_LIBRARY_PATH 
> to just reference their libs then we can fail to load the native Hadoop libs.
> This is currently mitigated by having Tez rely on the MapReduce admin 
> properties in many cases, but Tez should provide its own admin settings to 
> match the Tez-specific non-admin settings.



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

Reply via email to