You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2021/11/30 04:28:00 UTC

[jira] [Updated] (SPARK-37452) Char and Varchar breaks backward compatibility between v3 and v2

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

Dongjoon Hyun updated SPARK-37452:
----------------------------------
    Fix Version/s: 3.1.3

> 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.1.3, 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org