[jira] [Updated] (HIVE-23074) SchemaTool sql script execution errors when updating the metadata's schema

["John1Tang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-23074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John1Tang updated HIVE-23074:
-----------------------------
    Release Note: add "IF NOT EXISTS" for create & "IF EXISTS" for drop to keep consistency in the sql script  (was: add "IF NOT EXISTS" for create & "IF EXISTS" for drop to keep consistency and add " to avoid keywords in the sql script)

> SchemaTool sql script execution errors when updating the metadata's schema
> --------------------------------------------------------------------------
>
>                 Key: HIVE-23074
>                 URL: https://issues.apache.org/jira/browse/HIVE-23074
>             Project: Hive
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.1.2
>         Environment: running machine: centos7.2 
> metadata db: PostgreSQL 11.3 on x86_64-pc-linux-gnu
> hive version: upgrade from version 3.0.0 to 3.1.2
>            Reporter: John1Tang
>            Assignee: John1Tang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.1.2
>
>   Original Estimate: 1h
>          Time Spent: 0.5h
>  Remaining Estimate: 0.5h
>
> SchemaTool sql script executed with conflicts on indices and columns and missed " for avoiding keywords when updating the metadata's schema
> {code:java}
> bin/schematool -dbType postgres -upgradeSchemaFrom 3.0.0{code}
> went like this:
> {code:java}
> ALTER TABLE "GLOBAL_PRIVS" ADD COLUMN "AUTHORIZER" character varying(128) DEFAULT NULL::character varying
> Error: ERROR: column "AUTHORIZER" of relation "GLOBAL_PRIVS" already exists (state=42701,code=0){code}
> {code:java}
> ALTER TABLE COMPLETED_TXN_COMPONENTS ADD COLUMN IF NOT EXISTS CTC_UPDATE_DELETE char(1) NULL
> Error: ERROR: relation "completed_txn_components" does not exist (state=42P01,code=0)
> {code}
> I've already come up with a solution and created a pull request for this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)