spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yin Huai (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-16033) DataFrameWriter.partitionBy() can't be used together with DataFrameWriter.insertInto()
Date Sat, 18 Jun 2016 03:14:05 GMT

     [ https://issues.apache.org/jira/browse/SPARK-16033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yin Huai resolved SPARK-16033.
------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Issue resolved by pull request 13747
[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
>             Fix For: 2.0.0
>
>
> 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


Mime
View raw message