You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2016/07/26 09:16:20 UTC
[jira] [Resolved] (SPARK-16675) Avoid per-record type dispatch in
JDBC when writing
[ https://issues.apache.org/jira/browse/SPARK-16675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-16675.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
Issue resolved by pull request 14323
[https://github.com/apache/spark/pull/14323]
> Avoid per-record type dispatch in JDBC when writing
> ---------------------------------------------------
>
> Key: SPARK-16675
> URL: https://issues.apache.org/jira/browse/SPARK-16675
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.1.0
> Reporter: Hyukjin Kwon
> Assignee: Hyukjin Kwon
> Fix For: 2.1.0
>
>
> This is similar with https://issues.apache.org/jira/browse/SPARK-16351.
> Currently, {{JdbcUtils.savePartition}} is doing type-based dispatch for each row to write appropriate values.
> So, appropriate writers can be created first according to the schema, and then apply them to each row. This approach is similar with {{CatalystWriteSupport}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org