Sorry for the confusion, the problem is not with the MySQL version upgrade - I have indeed performed the upgrade by doing a mysqldump and restoring the data. The problem is with how Hive 0.7.1 is interacting with the same metastore data on a different version of MySQL server.
> Date: Mon, 5 Nov 2012 18:31:37 -0500 > Subject: Re: Hive 0.7.1 with MySQL 5.5 as metastore > From: edlinuxg...@gmail.com > To: user@hive.apache.org > > Moving underlying data files around is not the correct way to perform > an upgrade. > > https://dev.mysql.com/doc/refman/5.5/en/upgrading-from-previous-series.html > > I would do a mysqldump and then re-insert the data for maximum comparability. > > On Mon, Nov 5, 2012 at 6:21 PM, Venkatesh Kavuluri > <vkavul...@outlook.com> wrote: > > I am working on copying existing Hive metadata (Hive 0.7.1 with MySQL 5.1) > > to a new cluster environment (Hive 0.7.1 with MySQL 5.5). I copied over the > > metastore tables and modified the data under SDS (sub-directories) table to > > reflect the new data path. However I am getting MySQL integrity constraint > > violation against SDS.SD_ID column while trying to create new Hive tables. > > Is this a problem with the MySQL version I am using ? Does Hive 0.7.1 > > support MySQL 5.5 as the metastore. > > > > Thanks, > > Venkatesh
