[
https://issues.apache.org/jira/browse/HIVE-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174109#comment-16174109
]
Hive QA commented on HIVE-17483:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12888033/HIVE-17483.6.patch
{color:green}SUCCESS:{color} +1 due to 6 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 19 failed/errored test(s), 11053 tests
executed
*Failed tests:*
{noformat}
TestAccumuloCliDriver - did not produce a TEST-*.xml file (likely timed out)
(batchId=230)
TestDummy - did not produce a TEST-*.xml file (likely timed out) (batchId=230)
org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[mapjoin2]
(batchId=239)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[create_view] (batchId=39)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[udf_mask_hash]
(batchId=28)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[union_fast_stats]
(batchId=156)
org.apache.hadoop.hive.cli.TestMiniSparkOnYarnCliDriver.testCliDriver[bucketizedhiveinputformat]
(batchId=170)
org.apache.hadoop.hive.cli.TestMiniSparkOnYarnCliDriver.testCliDriver[spark_explainuser_1]
(batchId=170)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[drop_table_failure2]
(batchId=89)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query23]
(batchId=234)
org.apache.hadoop.hive.ql.lockmgr.TestDbTxnManager2.testShowTablesLock
(batchId=282)
org.apache.hive.service.cli.session.TestHiveSessionImpl.testLeakOperationHandle
(batchId=223)
org.apache.hive.service.cli.session.TestQueryDisplay.testQueryDisplay
(batchId=223)
org.apache.hive.service.cli.session.TestQueryDisplay.testWebUI (batchId=223)
org.apache.hive.service.cli.session.TestSessionManagerMetrics.testAbandonedSessionMetrics
(batchId=197)
org.apache.hive.service.cli.session.TestSessionManagerMetrics.testActiveSessionMetrics
(batchId=197)
org.apache.hive.service.cli.session.TestSessionManagerMetrics.testActiveSessionTimeMetrics
(batchId=197)
org.apache.hive.service.cli.session.TestSessionManagerMetrics.testOpenSessionMetrics
(batchId=197)
org.apache.hive.service.cli.session.TestSessionManagerMetrics.testOpenSessionTimeMetrics
(batchId=197)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/6911/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/6911/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-6911/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 19 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12888033 - PreCommit-HIVE-Build
> HS2 kill command to kill queries using query id
> -----------------------------------------------
>
> Key: HIVE-17483
> URL: https://issues.apache.org/jira/browse/HIVE-17483
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: Thejas M Nair
> Assignee: Teddy Choi
> Attachments: HIVE-17483.1.patch, HIVE-17483.2.patch,
> HIVE-17483.2.patch, HIVE-17483.3.patch, HIVE-17483.4.patch,
> HIVE-17483.5.patch, HIVE-17483.6.patch
>
>
> For administrators, it is important to be able to kill queries if required.
> Currently, there is no clean way to do it.
> It would help to have a "kill query <query id>" command that can be run using
> odbc/jdbc against a HiveServer2 instance, to kill a query with that queryid
> running in that instance.
> Authorization will have to be done to ensure that the user that is invoking
> the API is allowed to perform this action.
> In case of SQL std authorization, this would require admin role.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
