hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yongzhi Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-21337) HMS Metadata migration from Postgres/Derby to other DBs fail
Date Fri, 01 Mar 2019 00:24:00 GMT

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

Yongzhi Chen commented on HIVE-21337:
-------------------------------------

In order not to lost data (even comment) for Postgres DB after upgrade hive, we should keep
the old value for newer version for the Postgres. Therefore, IMO increase other DB's comment
size is better choice.

> HMS Metadata migration from Postgres/Derby to other DBs fail
> ------------------------------------------------------------
>
>                 Key: HIVE-21337
>                 URL: https://issues.apache.org/jira/browse/HIVE-21337
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 3.0.0
>            Reporter: Naveen Gangam
>            Assignee: Naveen Gangam
>            Priority: Minor
>         Attachments: HIVE-21337.patch
>
>
> Customer recently was migrating from Postgres to Oracle for HMS metastore. During import
of the [exported] data from HMS metastore from postgres, failures are seen as the COLUMNS_V2.COMMENT
is 4000 bytes long whereas oracle and other schemas define it to be 256 bytes.
> This inconsistency in the schema makes the migration cumbersome and manual. This jira
makes this column consistent in length across all databases.



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

Mime
View raw message