You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2014/11/01 01:40:33 UTC

[jira] [Created] (HIVE-8691) Hive sometimes cannot be upgraded to 14 using SchemaTool if original database was autocreate-created

Sergey Shelukhin created HIVE-8691:
--------------------------------------

             Summary: Hive sometimes cannot be upgraded to 14 using SchemaTool if original database was autocreate-created
                 Key: HIVE-8691
                 URL: https://issues.apache.org/jira/browse/HIVE-8691
             Project: Hive
          Issue Type: Bug
            Reporter: Sergey Shelukhin


Lazy creation doesn't make sure all tables are present.
Writing defensive upgrade scripts will make them extremely ugly. 
I guess we can accept it for earlier versions... for upgrading from 14 (15?) onwards, perhaps we can have a flag that would indicate the script has been run (as opposed to autoCreate). If not, we'd run database creation script for the original version. All these would need to be made idempotent in a sense that they should pass when the database was already created. It looks like e.g. mysql scripts already are (at least for create table statements) but mssql are not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)