You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Richard Zang (JIRA)" <ji...@apache.org> on 2015/06/05 23:47:00 UTC
[jira] [Updated] (AMBARI-11738) Remove "Max idle tez session
length" from hive enhanced config tab
[ https://issues.apache.org/jira/browse/AMBARI-11738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Zang updated AMBARI-11738:
----------------------------------
Attachment: AMBARI-11738.patch
> 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)