[jira] [Commented] (HIVE-21594) Warning regarding multiple MOVE triggers is logged even if conflicting triggers are both KILL

["Prasanth Jayachandran (JIRA)" <ji...@apache.org>]

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

Prasanth Jayachandran commented on HIVE-21594:
----------------------------------------------

[~bgoerlitz] I will cover this in HIVE-21597 since this is logging only change.

> Warning regarding multiple MOVE triggers is logged even if conflicting triggers are both KILL
> ---------------------------------------------------------------------------------------------
>
>                 Key: HIVE-21594
>                 URL: https://issues.apache.org/jira/browse/HIVE-21594
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 4.0.0, 3.2.0
>            Reporter: Brian Goerlitz
>            Assignee: Prasanth Jayachandran
>            Priority: Minor
>
> The following in TriggerValidatorRunnable will log a WARN about conflicting MOVE triggers even if the previous trigger violated was a KILL trigger.
>  
> {code:java}
> } else { 
> // if multiple MOVE happens, only first move will be chosen
> LOG.warn("Conflicting MOVE triggers ({} and {}). Choosing the first MOVE trigger: {}", existingTrigger, currentTrigger, existingTrigger.getName());
> {code}
>  
> This logging makes sense if the code broke out of the triggers loop on the first encountered KILL trigger violation, but this currently does not happen.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)