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

Hadoop QA commented on AMBARI-17360:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12812433/AMBARI-17360.branch-2.4.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 
contrib/views/hive-next contrib/views/hive 

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

This message is automatically generated.

> IE browser fetches Hive view API call results from browser cache, hence does 
> not update the query status
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17360
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17360
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.2.2
>            Reporter: DIPAYAN BHOWMICK
>            Assignee: DIPAYAN BHOWMICK
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17360.branch-2.4.patch
>
>
> Hive view polls GET calls to fetch job status,
> Since the GET call URL is same everytime it is fired, IE browsers tend to 
> fetch results from cache.
> For queries like "select *" without any clause, the job status is returned 
> 'Successful' immediately in the first call and no further polling is 
> required, hence the result is rendered on UI correctly.
> For queries with special clause like group by, where or order by clause, the 
> result is not returned, a job id is returned.
> The first call to poll the job status is cached in the browser, which returns 
> the query status as "Running". The results for the subsequent calls don't get 
> displayed.
> This issue is specific to IE browser. Issue is reproducible for Ambari 2.4 
> hive view on Edge 10 browser as well.



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

Reply via email to