[jira] [Commented] (HIVE-17508) Implement global execution triggers based on counters

["Hive QA (JIRA)" <ji...@apache.org>]

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

Hive QA commented on HIVE-17508:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12890833/HIVE-17508.9.patch

{color:green}SUCCESS:{color} +1 due to 5 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 11219 tests executed
*Failed tests:*
{noformat}
TestThriftCLIServiceWithBinary - did not produce a TEST-*.xml file (likely timed out) (batchId=223)
org.apache.hadoop.hive.cli.TestAccumuloCliDriver.testCliDriver[accumulo_predicate_pushdown] (batchId=231)
org.apache.hadoop.hive.cli.TestAccumuloCliDriver.testCliDriver[accumulo_single_sourced_multi_insert] (batchId=231)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[optimize_nullscan] (batchId=162)
org.apache.hadoop.hive.cli.TestMiniSparkOnYarnCliDriver.testCliDriver[spark_explainuser_1] (batchId=171)
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/7173/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/7173/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-7173/

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: 5 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12890833 - PreCommit-HIVE-Build

> Implement global execution triggers based on counters
> -----------------------------------------------------
>
>                 Key: HIVE-17508
>                 URL: https://issues.apache.org/jira/browse/HIVE-17508
>             Project: Hive
>          Issue Type: Sub-task
>    Affects Versions: 3.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>         Attachments: HIVE-17508.1.patch, HIVE-17508.2.patch, HIVE-17508.3.patch, HIVE-17508.3.patch, HIVE-17508.4.patch, HIVE-17508.5.patch, HIVE-17508.6.patch, HIVE-17508.7.patch, HIVE-17508.8.patch, HIVE-17508.9.patch, HIVE-17508.WIP.2.patch, HIVE-17508.WIP.patch
>
>
> Workload management can defined Triggers that are bound to a resource plan. Each trigger can have a trigger expression and an action associated with it. Trigger expressions are evaluated at runtime after configurable check interval, based on which actions like killing a query, moving a query to different pool etc. will get invoked. Simple execution trigger could be something like
> {code}
> CREATE TRIGGER slow_query IN global
> WHEN execution_time_ms > 10000
> MOVE TO slow_queue
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)