[
https://issues.apache.org/jira/browse/HIVE-18095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293361#comment-16293361
]
Sergey Shelukhin commented on HIVE-18095:
-----------------------------------------
That would require having some reserved name and special casing it everywhere
(e.g. you cannot change policy/etc. for it, WM class has to skip it in all the
calculations and processing, etc.).
Also if we do implement global flag, we'd have a similar flag and commands
anyway because it will have another different type of treatment (triggers apply
to queries in all pools).
> add a unmanaged flag to triggers (applies to container based sessions)
> ----------------------------------------------------------------------
>
> Key: HIVE-18095
> URL: https://issues.apache.org/jira/browse/HIVE-18095
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-18095.nogen.patch, HIVE-18095.patch
>
>
> cc [~prasanth_j]
> It should be impossible to attach global triggers for pools. Setting global
> flag should probably automatically remove attachments to pools.
> Global triggers would only support actions that Tez supports (for simplicity;
> also, for now, move doesn't make a lot of sense because the trigger would
> apply again after the move).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
