[
https://issues.apache.org/jira/browse/HIVE-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794870#comment-16794870
]
Ashutosh Bapat commented on HIVE-21462:
---------------------------------------
Since dropping an unnamed constraint requires some SQL code in SQL server, it's
better to name all the constraints explicitly to keep the scripts simple. So,
there are additional changes in the scripts to name the new constraints created.
> Upgrading SQL server backed metastore when changing data type of a column
> with constraints
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-21462
> URL: https://issues.apache.org/jira/browse/HIVE-21462
> Project: Hive
> Issue Type: Bug
> Components: Standalone Metastore
> Reporter: Ashutosh Bapat
> Assignee: Ashutosh Bapat
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Original Estimate: 24h
> Time Spent: 10m
> Remaining Estimate: 23h 50m
>
> SQL server does not allow changing data type of a column which has a
> constraint or an index on it. The constraint or the index needs to be dropped
> before changing the data type and needs to be recreated after that. Metastore
> upgrade scripts aren't doing this and thus upgrade fails.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
