[HIVE-8691] Hive sometimes cannot be upgraded using SchemaTool if original database was autocreate-created - ASF JIRA

Log work

Agile Board

Rank to Top

Rank to Bottom

Bulk Copy Attachments

Bulk Move Attachments

Add vote

Voters

Watch issue

Watchers

Create sub-task

Convert to sub-task

Move

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: None
Labels:
None

Description

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.