[jira] [Updated] (HIVE-20524) Schema Evolution checking is broken in going from ver 2 to ver 3 for ALTER TABLE CHAR to DECIMAL

["Matt McCline (JIRA)" <ji...@apache.org>]

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

Matt McCline updated HIVE-20524:
--------------------------------
    Summary: Schema Evolution checking is broken in going from ver 2 to ver 3 for ALTER TABLE CHAR to DECIMAL  (was: Schema Evolution checking is broken in 3.0 for CHAR/VARCHAR/DECIMAL)

> Schema Evolution checking is broken in going from ver 2 to ver 3 for ALTER TABLE CHAR to DECIMAL
> ------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-20524
>                 URL: https://issues.apache.org/jira/browse/HIVE-20524
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>            Reporter: Matt McCline
>            Assignee: Matt McCline
>            Priority: Critical
>         Attachments: HIVE-20524.01.patch
>
>
> The new org.apache.hadoop.hive.metastore.ColumnType class under hive version 3 hive-standalone-metadata-server method checkColTypeChangeCompatible lost a version 2 series bug fix that drops CHAR/VARCHAR (and DECIMAL I think) type decorations when checking for Schema Evolution compatibility.
> Hive1 version 2 did undecoratedTypeName(oldType) and Hive2 version performed the logic in TypeInfoUtils.implicitConvertible on the PrimitiveCategory not the raw type string.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)