hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17508) Implement global execution triggers based on counters
Date Wed, 18 Oct 2017 07:29:00 GMT

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

Lefty Leverenz commented on HIVE-17508:
---------------------------------------

Doc note:  This adds *hive.trigger.validation.interval.ms* to HiveConf.java, which needs to
be documented in the wiki.  Perhaps there will be a new section in Configuration Properties;
otherwise it belongs in the general section for query configs.

* [Configuration Properties | https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties]

Will the general documentation be covered with umbrella HIVE-17481?

Added a TODOC3.0 label.

> 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
>              Labels: TODOC3.0
>             Fix For: 3.0.0
>
>         Attachments: HIVE-17508.1.patch, HIVE-17508.10.patch, HIVE-17508.11.patch, HIVE-17508.12.patch,
HIVE-17508.13.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)

Mime
View raw message