[ 
https://issues.apache.org/jira/browse/HIVE-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797416#comment-16797416
 ] 

Hive QA commented on HIVE-21462:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12963097/HIVE-21462.02.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 15832 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/16592/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16592/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16592/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12963097 - PreCommit-HIVE-Build

> 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
>
>         Attachments: HIVE-21462.01.patch, HIVE-21462.02.patch
>
>   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)

Reply via email to