[
https://issues.apache.org/jira/browse/AMBARI-11738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575552#comment-14575552
]
Hadoop QA commented on AMBARI-11738:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12738067/AMBARI-11738.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3069//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3069//console
This message is automatically generated.
> Remove "Max idle tez session length" from hive enhanced config tab
> ------------------------------------------------------------------
>
> Key: AMBARI-11738
> URL: https://issues.apache.org/jira/browse/AMBARI-11738
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Richard Zang
> Assignee: Richard Zang
> Fix For: 2.1.0
>
> Attachments: AMBARI-11738.patch
>
>
> "Max idle tez session length" will be removed from the Hive config page, as
> having this control persist tez.session.am.dag.submit.timeout.secs in
> hiveserver2-site.xml won't work from the Hive + Tez perspective (or will not
> always work).
> If the user needs to customize tez.session.am.dag.submit.timeout.secs, the
> user can go to Tez > Config page (it is already exposed there).
> If the user needs to change this value to accommodate different Hive
> applications, etc., Config Groups can be used to apply host-specific values.
> Each host has one copy of tez-site.xml used for all Tez applications such as
> Hive and Pig. Eventually we want to have tez-site.xml that is specific to
> HiveServer2, but this is out of scope for Ambari-2.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
