[
https://issues.apache.org/jira/browse/SPARK-37452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kent Yao resolved SPARK-37452.
------------------------------
Fix Version/s: 3.2.1
3.3.0
Resolution: Fixed
Issue resolved by https://github.com/apache/spark/pull/34697
> Char and Varchar breaks backward compatibility between v3 and v2
> ----------------------------------------------------------------
>
> Key: SPARK-37452
> URL: https://issues.apache.org/jira/browse/SPARK-37452
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.1.2, 3.2.0
> Reporter: Kent Yao
> Assignee: Kent Yao
> Priority: Major
> Fix For: 3.2.1, 3.3.0
>
>
> We will store table schema in table properties for the read-side to restore.
> In Spark 3.1, we add char/varchar support natively. In some commands like
> `create table`, `alter table` with these types, the char(n) or varchar(n)
> will be stored directly to those properties. If a user uses Spark 2 to read
> such a table it will fail to parse the schema.
> A table can be a newly created one by Spark 3.1 and later or an existing one
> modified by Spark 3.1 and on.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
