You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Thang Long Vu (Jira)" <ji...@apache.org> on 2025/03/03 14:16:00 UTC
[jira] [Created] (SPARK-51370) Code clarity improvements for INSERT INTO parsing codes in AstBuilder.scala
Thang Long Vu created SPARK-51370:
-------------------------------------
Summary: Code clarity improvements for INSERT INTO parsing codes in AstBuilder.scala
Key: SPARK-51370
URL: https://issues.apache.org/jira/browse/SPARK-51370
Project: Spark
Issue Type: Improvement
Components: SQL
Affects Versions: 4.1
Reporter: Thang Long Vu
# Use Case Class instead of Tuple to store the parsing results of INSERT INTO SQL Statements, this gives name to multiple return fields which is clearer and easier to follow the fields.
# When creating {{{}InsertIntoStatement{}}}, mixing by-name and by-position arguments is unexpected and it's unclear how the positional arguments after the named one are resolved. Thus, we only use by-name arguments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org