[
https://issues.apache.org/jira/browse/HIVE-17508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204214#comment-16204214
]
Sergey Shelukhin commented on HIVE-17508:
-----------------------------------------
Left some smaller comments on RB. My main concern is, how does it work with WM
that we pass all the queries and all the triggers to trigger enforcement? How
does it make sure that triggers apply only to the queries in their own pool?
> 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.10.patch,
> HIVE-17508.11.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)
