You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2017/12/14 02:00:00 UTC

[jira] [Commented] (HIVE-18095) add a unmanaged flag to triggers (applies to container based sessions)

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

Sergey Shelukhin commented on HIVE-18095:
-----------------------------------------

Btw this only adds unmanaged flag which is more clear and can coexist with pools. I am not sure global flag makes sense... presumably most triggers will be pool specific. Maybe we can add it in phase 2 :)

> 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)