[
https://issues.apache.org/jira/browse/HIVE-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Steinbach updated HIVE-2011:
---------------------------------
Attachment: HIVE-2011.3.patch.txt
HIVE-2011.3.patch.txt:
* Fixed errors in Derby schema scripts caused by accidentally picking up wrong
DataNucleus (and wrong IdentifierFactory) during original schema generation run.
* Added a couple usage notes to the Derby and MySQL READMEs related to the ij
and mysqldump utilities.
Testing:
# Created Derby and MySQL schemas for 0.3.0 through 0.7.0 by starting Hive with
autoCreateSchema=true.
# Applied hive-schema-x.y.z.xxx.sql scripts to each of the previously created
DBs. Verified that these scripts complete without error, and that the resulting
DB schemas contain all tables.
# Applied the upgrade scripts to validated 0.5.0 and 0.6.0 DBs for Derby and
MySQL, and verified that all scripts complete without error.
# Validated the upgraded DBs by running Hive against the upgraded DB schema
with datanucleus.autoCreateSchema=false and datanucleus.validateSchema=true
> upgrade-0.6.0.mysql.sql script attempts to increase size of PK
> COLUMNS.TYPE_NAME to 4000
> ----------------------------------------------------------------------------------------
>
> Key: HIVE-2011
> URL: https://issues.apache.org/jira/browse/HIVE-2011
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.6.0
> Reporter: Carl Steinbach
> Assignee: Carl Steinbach
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: HIVE-2011.1.patch.txt, HIVE-2011.2.patch.txt,
> HIVE-2011.2.patch.txt, HIVE-2011.3.patch.txt
>
>
> {code}
> # mysql flumenewresearch < upgrade-0.6.0.mysql.sql
> ERROR 1071 (42000) at line 16: Specified key was too long; max key length is
> 767 bytes
> {code}
> Here's the cause of the problem from upgrade-0.6.0.mysql.sql:
> {code}
> ...
> ALTER TABLE `COLUMNS` MODIFY `TYPE_NAME` VARCHAR(4000);
> ...
> ALTER TABLE `COLUMNS` DROP PRIMARY KEY;
> ALTER TABLE `COLUMNS` ADD PRIMARY KEY (`SD_ID`, `COLUMN_NAME`);
> ...
> {code}
> We need to make sure that the PK on COLUMNS.TYPE_NAME is dropped before the
> size of the column is bumped to 4000.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
