[
https://issues.apache.org/jira/browse/SPARK-51370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gengliang Wang resolved SPARK-51370.
------------------------------------
Fix Version/s: 4.1.0
Resolution: Fixed
Issue resolved by pull request 50135
[https://github.com/apache/spark/pull/50135]
> 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
> Assignee: Thang Long Vu
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> # 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
