[
https://issues.apache.org/jira/browse/AMBARI-13806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008488#comment-15008488
]
Hadoop QA commented on AMBARI-13806:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12772673/AMBARI-13806.2_branch-2.1.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 1 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
contrib/views/hive.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4305//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4305//console
This message is automatically generated.
> Multi statement queries with errors after the first statement cause orphaned
> AMs
> --------------------------------------------------------------------------------
>
> Key: AMBARI-13806
> URL: https://issues.apache.org/jira/browse/AMBARI-13806
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.1.2
> Reporter: DIPAYAN BHOWMICK
> Assignee: DIPAYAN BHOWMICK
> Fix For: 2.1.3
>
> Attachments: AMBARI-13806.2_branch-2.1.patch,
> AMBARI-13806_branch-2.1.patch
>
>
> If you run a query like:
> {code}
> select count(*) from account;
> ;
> {code}
> An AM will get started, the query will run, you'll get an H110 error and
> there will be no Kill Session button. Meanwhile the AM is still running and
> holding on to containers.
> Ambari 2.1.2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
