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 2020/12/06 09:27:00 UTC
[jira] [Assigned] (SPARK-33676) Require exact matched partition
spec to schema in ADD/DROP PARTITION
[ https://issues.apache.org/jira/browse/SPARK-33676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-33676:
------------------------------------
Assignee: Apache Spark
> Require exact matched partition spec to schema in ADD/DROP PARTITION
> --------------------------------------------------------------------
>
> Key: SPARK-33676
> URL: https://issues.apache.org/jira/browse/SPARK-33676
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Maxim Gekk
> Assignee: Apache Spark
> Priority: Major
>
> The V1 implementation of ALTER TABLE .. ADD/DROP PARTITION fails when the partition spec doesn't exactly match to the partition schema:
> {code:sql}
> ALTER TABLE tab1 ADD PARTITION (A='9')
> Partition spec is invalid. The spec (a) must match the partition spec (a, b) defined in table '`dbx`.`tab1`';
> org.apache.spark.sql.AnalysisException: Partition spec is invalid. The spec (a) must match the partition spec (a, b) defined in table '`dbx`.`tab1`';
> at org.apache.spark.sql.catalyst.catalog.SessionCatalog.$anonfun$requireExactMatchedPartitionSpec$1(SessionCatalog.scala:1173)
> at org.apache.spark.sql.catalyst.catalog.SessionCatalog.$anonfun$requireExactMatchedPartitionSpec$1$adapted(SessionCatalog.scala:1171)
> at scala.collection.immutable.List.foreach(List.scala:392)
> {code}
> for a table partitioned by "a", "b" but the V2 implementation add the wrong partition silently.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org