ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14989) Inconsistent HIVE CBO setting presentation
Date Thu, 11 Feb 2016 02:55:18 GMT

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

Hadoop QA commented on AMBARI-14989:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12787240/AMBARI-14989.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 4 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 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 ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5304//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5304//console

This message is automatically generated.

> Inconsistent HIVE CBO setting presentation
> ------------------------------------------
>
>                 Key: AMBARI-14989
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14989
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-14989.patch
>
>
> Hive in Ambari shows enabling CBO at two places "settings tab" and "Advanced tab". By
default both of them have same value but there is a possibility that due to some user actions,
values at these two places may differ and create confusion.



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

Mime
View raw message