Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 17 Sep 2013 05:58:57 +0000 (UTC)
From: "Prasad Mujumdar (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12618540.1354524984022.145122.1379397537581@arcas>
In-Reply-To: <JIRA.12618540.1354524984022@arcas>
References: <JIRA.12618540.1354524984022@arcas>
Subject: [jira] [Updated] (HIVE-3764) Support metastore version consistency
 check
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasad Mujumdar updated HIVE-3764:
----------------------------------

    Attachment: HIVE-3764.1.patch

Patch specific to version consistency check
                
> Support metastore version consistency check
> -------------------------------------------
>
>                 Key: HIVE-3764
>                 URL: https://issues.apache.org/jira/browse/HIVE-3764
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 0.8.0, 0.9.0, 0.10.0, 0.11.0
>            Reporter: Prasad Mujumdar
>            Assignee: Prasad Mujumdar
>             Fix For: 0.12.0
>
>         Attachments: HIVE-3764-0.13-addional-file.patch, HIVE-3764.1.patch, HIVE-3764.4.patch, HIVE-3764.4.patch
>
>
> Today there's no version/compatibility information stored in hive metastore. Also the datanucleus configuration property to automatically create missing tables is enabled by default. If you happen to start an older or newer hive or don't run the correct upgrade scripts during migration, the metastore would end up corrupted. The autoCreate schema is not always sufficient to upgrade metastore when migrating to newer release. It's not supported with all databases. Besides the migration often involves altering existing table, changing or moving data etc.
> Hence it's very useful to have some consistency check to make sure that hive is using correct metastore and for production systems the schema is not automatically by running hive.
> Besides it would be helpful to add a tool that can leverage this version information to figure out the required set of upgrade scripts, and execute those against the configured metastore. Now that Hive includes Beeline client, it can be used to execute the scripts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira