[
https://issues.apache.org/jira/browse/HIVE-21337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naveen Gangam updated HIVE-21337:
---------------------------------
Attachment: HIVE-21337.patch
Status: Patch Available (was: Open)
I am just fixing the schemas to be consistent going forward. I dont think the
upgrade path will be clean if we add {{ALTER TABLE .. }} to the upgrade script
to reduce the existing 4000 length to be 256. If there are some rows, that
contain value of > 256 chars for this column, the behavior across different
databases is different. Some truncate the value while some fail.
> 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)
