[jira] [Commented] (SPARK-42750) Support INSERT INTO by name

2023-05-06 Thread Jia Fan (Jira)


[ 
https://issues.apache.org/jira/browse/SPARK-42750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720272#comment-17720272
 ] 

Jia Fan commented on SPARK-42750:
-

Please review https://github.com/apache/spark/pull/40908

> Support INSERT INTO by name
> ---
>
> Key: SPARK-42750
> URL: https://issues.apache.org/jira/browse/SPARK-42750
> Project: Spark
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 3.4.0
>Reporter: Jose Torres
>Priority: Major
>
> In some use cases, users have incoming dataframes with fixed column names 
> which might differ from the canonical order. Currently there's no way to 
> handle this easily through the INSERT INTO API - the user has to make sure 
> the columns are in the right order as they would when inserting a tuple. We 
> should add an optional BY NAME clause, such that:
> INSERT INTO tgt BY NAME 
> takes each column of  and inserts it into the column in `tgt` which 
> has the same name according to the configured `resolver` logic.



--
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



[jira] [Commented] (SPARK-42750) Support INSERT INTO by name

2023-03-14 Thread Xinsen (Jira)


[ 
https://issues.apache.org/jira/browse/SPARK-42750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700509#comment-17700509
 ] 

Xinsen commented on SPARK-42750:


May I solve it? I'm interested in this. And by the way, does it just include 
inserting into hive table and hdfs file, or it includes jdbc tables like MySQL 
table?

> Support INSERT INTO by name
> ---
>
> Key: SPARK-42750
> URL: https://issues.apache.org/jira/browse/SPARK-42750
> Project: Spark
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 3.4.0
>Reporter: Jose Torres
>Priority: Major
>
> In some use cases, users have incoming dataframes with fixed column names 
> which might differ from the canonical order. Currently there's no way to 
> handle this easily through the INSERT INTO API - the user has to make sure 
> the columns are in the right order as they would when inserting a tuple. We 
> should add an optional BY NAME clause, such that:
> INSERT INTO tgt BY NAME 
> takes each column of  and inserts it into the column in `tgt` which 
> has the same name according to the configured `resolver` logic.



--
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