You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xianyin Xin (Jira)" <ji...@apache.org> on 2020/06/29 06:06:00 UTC
[jira] [Created] (SPARK-32127) Check rules for MERGE INTO should
use MergeAction.condition other than MeregAction.children
Xianyin Xin created SPARK-32127:
-----------------------------------
Summary: Check rules for MERGE INTO should use MergeAction.condition other than MeregAction.children
Key: SPARK-32127
URL: https://issues.apache.org/jira/browse/SPARK-32127
Project: Spark
Issue Type: Improvement
Components: SQL
Affects Versions: 3.0.0
Reporter: Xianyin Xin
[SPARK-30924|https://issues.apache.org/jira/browse/SPARK-30924] adds some check rules for MERGE INTO one of which ensures the first MATCHED clause must have a condition. However, it uses {MergeAction.children} in the checking which is not accurate for the case, and it lets the below case pass the check:
{code:scala}
MERGE INTO testcat1.ns1.ns2.tbl AS target
xxx
WHEN MATCHED THEN UPDATE SET target.col2 = source.col2
WHEN MATCHED THEN DELETE
xxx
{code}
We should use {MergeAction.condition} instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org