[ https://issues.apache.org/jira/browse/HIVE-22234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939990#comment-16939990 ]
Hive QA commented on HIVE-22234: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12981576/HIVE-22234.04.patch {color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified. {color:green}SUCCESS:{color} +1 due to 17011 tests passed Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/18768/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/18768/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-18768/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Executing org.apache.hive.ptest.execution.PrepPhase Executing org.apache.hive.ptest.execution.YetusPhase Executing org.apache.hive.ptest.execution.ExecutionPhase Executing org.apache.hive.ptest.execution.ReportingPhase {noformat} This message is automatically generated. ATTACHMENT ID: 12981576 - PreCommit-HIVE-Build > 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: 40m > 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)