[
https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574918#comment-13574918
]
Hudson commented on HIVE-3999:
------------------------------
Integrated in Hive-trunk-hadoop2 #112 (See
[https://builds.apache.org/job/Hive-trunk-hadoop2/112/])
HIVE-3999 Mysql metastore upgrade script will end up with different schema
than
the full schema load (Jarek and Mark via namit) (Revision 1443952)
Result = FAILURE
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443952
Files :
* /hive/trunk/metastore/scripts/upgrade/mysql/011-HIVE-3649.mysql.sql
> 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
> Fix For: 0.11.0
>
> Attachments: mysql_upgrade_issue.patch
>
>
> 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
