[ 
https://issues.apache.org/jira/browse/HIVE-23074?focusedWorklogId=452871&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-452871
 ]

ASF GitHub Bot logged work on HIVE-23074:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Jun/20 08:56
            Start Date: 30/Jun/20 08:56
    Worklog Time Spent: 10m 
      Work Description: John1Tang commented on pull request #967:
URL: https://github.com/apache/hive/pull/967#issuecomment-651657855


   my pull request only changed the postgres schematool, this test failed with 
hive jdbc storage handler...


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 452871)
    Time Spent: 1h 10m  (was: 1h)

> 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: 1h 10m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to