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

Hadoop QA commented on AMBARI-16269:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12802408/AMBARI-16269.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:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

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

This message is automatically generated.

> Show background op window when Interactive query is enabled/disabled
> --------------------------------------------------------------------
>
>                 Key: AMBARI-16269
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16269
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16269.patch
>
>
> *STR:*
> # Deploy a cluster with Hive service
> # Post deployment of the cluster, Enable interactive query on Hive service 
> page
> # Click on save button to save configuration.
> *Actual behavior:* Confirmation popup about configurations successfully saved 
> is shown to user. Background ops blinks showing running requests
> *Expected behavior:* On clicking "ok" on popup about configurations 
> successfully saved, background op window should come up showing running 
> requests. Thus making it explicit to the user about ongoing operations on 
> saving configurations. 
> NOTE: Background opertaion window should be shown only if saving 
> Enable/Disable interactive query leads to background ops.



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

Reply via email to