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-16771) Schematool should use MetastoreSchemaInfo to get the metastore schema version from database
Date Wed, 31 May 2017 16:59:04 GMT

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

Naveen Gangam commented on HIVE-16771:
--------------------------------------

Changes look good to me as well. So +1 for me.

> Schematool should use MetastoreSchemaInfo to get the metastore schema version from database
> -------------------------------------------------------------------------------------------
>
>                 Key: HIVE-16771
>                 URL: https://issues.apache.org/jira/browse/HIVE-16771
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>         Attachments: HIVE-16771.01.patch, HIVE-16771.02.patch, HIVE-16771.03.patch, HIVE-16771.04.patch
>
>
> HIVE-16723 gives the ability to have a custom MetastoreSchemaInfo implementation to manage
schema upgrades and initialization if needed. In order to make HiveSchemaTool completely agnostic
it should depend on IMetastoreSchemaInfo implementation which is configured to get the metastore
schema version information from the database. It should also not assume the scripts directory
and hardcode it itself. It would rather ask MetastoreSchemaInfo class to get the metastore
scripts directory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message