You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2013/02/07 22:25:13 UTC

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

Jarek Jarcec Cecho created HIVE-3999:
----------------------------------------

             Summary: Mysql metastore upgrade script will end up with different schema than the full schema load
                 Key: HIVE-3999
                 URL: https://issues.apache.org/jira/browse/HIVE-3999
             Project: Hive
          Issue Type: Bug
          Components: Metastore
            Reporter: Jarek Jarcec Cecho


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

{code}
  `IS_STOREDASSUBDIRECTORIES` bit(1) NOT NULL,
{code}

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

{code}
ALTER TABLE `SDS` ADD `IS_STOREDASSUBDIRECTORIES` bit(1) ;
{code}

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


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira