You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2015/05/30 20:46:17 UTC

[jira] [Commented] (AMBARI-11562) The value of 'Max idle tez session length' from the default Hive config group can be changed when you are at setting of aother Hive config group

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

Aleksandr Kovalenko commented on AMBARI-11562:
----------------------------------------------

+1 for patch

> The value of 'Max idle tez session length' from the default Hive config group can be changed when you are at setting of aother Hive config group
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-11562
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11562
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11562.patch
>
>
> I created a new Hive config group, 'Tak Hive' and choose that group at 'Custom Services' of the installation wizard. All properties shows setting from the default Hive group and they are grayed out except for 'Max idle tez session length' as shown in the attached screenshot.
> You can actually change that value, for example, from 600 to 900. This results change in the value of the default Hive Config which is not supposed to happen. When you are at the new Hive Config group, you should not be able to change configs from the default Hive Config group.



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