hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-8691) Hive sometimes cannot be upgraded using SchemaTool if original database was autocreate-created
Date Sat, 01 Nov 2014 00:47:33 GMT

    [ https://issues.apache.org/jira/browse/HIVE-8691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192833#comment-14192833
] 

Sergey Shelukhin commented on HIVE-8691:
----------------------------------------

Perhaps VERSION table can be used for that

> Hive sometimes cannot be upgraded 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 (we cannot just not do
changes if tables do not exist; we'd have to create the stupid table and then do the changes)
> 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)

Mime
View raw message