hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "HBase Review Board (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1427) Provide metastore schema migration scripts (0.5 -> 0.6)
Date Sat, 02 Oct 2010 01:46:34 GMT

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

HBase Review Board commented on HIVE-1427:

Message from: "Carl Steinbach" <carl@cloudera.com>

This is an automatically generated e-mail. To reply, visit:

Review request for Hive Developers, namit jain, John Sichi, and Paul Yang.


This patch provides metastore schema upgrade scripts for MySQL and Derby based metastores.
Note that this patch includes the schema changes proposed in HIVE-1364.

This addresses bug HIVE-1427.


  metastore/scripts/upgrade/derby/README PRE-CREATION 
  metastore/scripts/upgrade/derby/upgrade-0.6.0.derby.sql PRE-CREATION 
  metastore/scripts/upgrade/mysql/README PRE-CREATION 
  metastore/scripts/upgrade/mysql/upgrade-0.6.0.mysql.sql PRE-CREATION 

Diff: http://review.cloudera.org/r/931/diff




> Provide metastore schema migration scripts (0.5 -> 0.6)
> -------------------------------------------------------
>                 Key: HIVE-1427
>                 URL: https://issues.apache.org/jira/browse/HIVE-1427
>             Project: Hadoop Hive
>          Issue Type: Task
>          Components: Metastore
>            Reporter: Carl Steinbach
>            Assignee: Carl Steinbach
>             Fix For: 0.6.0
>         Attachments: HIVE-1427.1.patch.txt
> At a minimum this ticket covers packaging up example MySQL migration scripts (cumulative
across all schema changes from 0.5 to 0.6) and explaining what to do with them in the release
> This is also probably a good point at which to decide and clearly state which Metastore
DBs we officially support in production, e.g. do we need to provide migration scripts for

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message