You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2016/06/18 00:41:05 UTC
[jira] [Commented] (SPARK-16033) DataFrameWriter.partitionBy()
can't be used together with DataFrameWriter.insertInto()
[ https://issues.apache.org/jira/browse/SPARK-16033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337343#comment-15337343 ]
Apache Spark commented on SPARK-16033:
--------------------------------------
User 'liancheng' has created a pull request for this issue:
https://github.com/apache/spark/pull/13747
> DataFrameWriter.partitionBy() can't be used together with DataFrameWriter.insertInto()
> --------------------------------------------------------------------------------------
>
> Key: SPARK-16033
> URL: https://issues.apache.org/jira/browse/SPARK-16033
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 2.0.0
> Reporter: Cheng Lian
> Assignee: Cheng Lian
>
> When inserting into an existing partitioned table, partitioning columns should always be determined by catalog metadata of the existing table to be inserted. Extra {{partitionBy()}} calls don't make sense, and mess up existing data because newly inserted data may have wrong partitioning directory layout.
--
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