Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <28535509.14901286399131989.JavaMail.jira@thor>
Date: Wed, 6 Oct 2010 17:05:31 -0400 (EDT)
From: "Namit Jain (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Resolved: (HIVE-1427) Provide metastore schema migration
 scripts (0.5 -> 0.6)
In-Reply-To: <33320483.2491277246450157.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Namit Jain resolved HIVE-1427.
------------------------------

       Resolution: Fixed
    Fix Version/s: 0.7.0
     Hadoop Flags: [Reviewed]

Committed in both 0.6 and trunk. Thanks Carl

> 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, 0.7.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 notes.
> 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 Derby?

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