hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-22234) Hive replication fails with table already exist error when replicating from old version of hive.
Date Mon, 08 Jun 2020 00:26:01 GMT

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

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

                Author: ASF GitHub Bot
            Created on: 08/Jun/20 00:25
            Start Date: 08/Jun/20 00:25
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] closed pull request #788:
URL: https://github.com/apache/hive/pull/788


   


----------------------------------------------------------------
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:
users@infra.apache.org


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

    Worklog Id:     (was: 442524)
    Time Spent: 1h  (was: 50m)

> Hive replication fails with table already exist error when replicating from old version
of hive.
> ------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-22234
>                 URL: https://issues.apache.org/jira/browse/HIVE-22234
>             Project: Hive
>          Issue Type: Bug
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-22234.01.patch, HIVE-22234.02.patch, HIVE-22234.03.patch, HIVE-22234.04.patch
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> HIve replication from old version where HIVE-22046 is not patched will not have engine
column set in the table column stats. This causes "ERROR: null value in column "ENGINE" violates
not-null constraint" error during create table while updating the column stats. As the column
stats are updated after the create table txn is committed, the next retry by HMS client throws
table already exist error. Need to update the ENGINE column to default value while importing
the table if the column value is not set. The column stat and create table in same txn can
be done as part of separate Jira.



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

Mime
View raw message