[
https://issues.apache.org/jira/browse/HIVE-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008690#comment-13008690
]
John Sichi commented on HIVE-2011:
----------------------------------
@Carl, I ran hive-schema-0.6.0.mysql.sql and two of the tablenames (dbs and
types) came out in lowercase; they should be ALLCAPS.
{noformat}
mysql> show tables;
+-------------------------+
| Tables_in_jvs_metastore |
+-------------------------+
| BUCKETING_COLS |
| COLUMNS |
| PARTITIONS |
| PARTITION_KEYS |
| PARTITION_KEY_VALS |
| PARTITION_PARAMS |
| SDS |
| SD_PARAMS |
| SERDES |
| SERDE_PARAMS |
| SORT_COLS |
| TABLE_PARAMS |
| TBLS |
| TYPE_FIELDS |
| dbs |
| types |
+-------------------------+
{noformat}
> 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
