[HIVE-14949] Add Cardinality Violation check in SQL MERGE stmt

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.0
• Component/s: Transactions
• Labels: TODOC2.2
• Assignee: Eugene Koifman
• Reporter: Eugene Koifman
• Created: 13/Oct/16 18:31
• Updated: 01/Oct/19 22:07
• Resolved: 30/Jan/17 20:31

Description

If > 1 row on source side matches the same row on target side that means that we are forced update (or delete) the same row in target more than once as part of the same SQL statement. This should raise an error per SQL Spec
ISO/IEC 9075-2:2011(E)
Section 14.2 under "General Rules" Item 6/Subitem a/Subitem 2/Subitem B

There is no sure way to do this via static analysis of the query.

Can we add something to ROJ operator to pay attention to ROW_ID of target side row and compare it with ROW_ID of target side of previous row output? If they are the same, that means > 1 source row matched.
Or perhaps just mark each row in the hash table that it matched. And if it matches again, throw an error.

Issue Links

• breaks: HIVE-15871 Cannot insert into target table because column number/types are different with hive.merge.cardinality.check=false
• is related to: HIVE-15839 Don't force cardinality check if only WHEN NOT MATCHED is specified