[HIVE-3999] Mysql metastore upgrade script will end up with different schema than the full schema load

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.11.0
• Component/s: Metastore
• Hadoop Flags: Reviewed
• Assignee: Jarek Jarcec Cecho
• Reporter: Jarek Jarcec Cecho
• Created: 07/Feb/13 21:24
• Updated: 16/May/13 21:10
• Resolved: 08/Feb/13 11:43

Description

I've noticed that the file hive-schema-0.10.0.mysql.sql is creating table SDS with following column:

  `IS_STOREDASSUBDIRECTORIES` bit(1) NOT NULL,

However the upgrade script 011-HIVE-3649.mysql.sql will create the column differently:

ALTER TABLE `SDS` ADD `IS_STOREDASSUBDIRECTORIES` bit(1) ;

Thus user will get slightly different schema each time - once with "NOT NULL" and secondly with "NULL" definition.

Issue Links

• is related to: HIVE-3995 PostgreSQL upgrade scripts are not valid
• is related to: HIVE-4024 Derby metastore update script will fail when upgrading from 0.9.0 to 0.10.0
• relates to: HIVE-3995 PostgreSQL upgrade scripts are not valid
• relates to: HIVE-3998 Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
• links to: Review board