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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.2.0, 4.0.0
• Assignee: Prasanth Jayachandran
• Reporter: Brian Goerlitz
• Created: 09/Apr/19 18:57
• Updated: 17/Apr/19 18:00
• Resolved: 17/Apr/19 18:00

Description

The following in TriggerValidatorRunnable will log a WARN about conflicting MOVE triggers even if the previous trigger violated was a KILL trigger.

 

} 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());

 

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.

Issue Links

• Is contained by: HIVE-21597 WM trigger validation should happen at the time of create or alter