hive-issues mailing list archives

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

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

Naveen Gangam commented on HIVE-21337:
--------------------------------------

[~ychena] Technically no reason. But given that it is a field for {{Comment}} for a column
in a table, I dint think it was important enough to increase it that dramatically. If it was
for {{comment}} for database or table entities, maybe we can explain it somehow. Given there
could be millions of rows in this COLUMNS_V2 table, dint seem it is worth to increase the
size of each row.
But I am ok, either way. 

> 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