From issues-return-158102-archive-asf-public=cust-asf.ponee.io@hive.apache.org Mon May 20 04:02:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 3277718076D for ; Mon, 20 May 2019 06:02:02 +0200 (CEST) Received: (qmail 23561 invoked by uid 500); 20 May 2019 04:02:01 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 23473 invoked by uid 99); 20 May 2019 04:02:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 May 2019 04:02:01 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6E6CEE29BD for ; Mon, 20 May 2019 04:02:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2126D25807 for ; Mon, 20 May 2019 04:02:00 +0000 (UTC) Date: Mon, 20 May 2019 04:02:00 +0000 (UTC) From: "Hive QA (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-21731) Hive import fails, post upgrade of source 3.0 cluster, to a target 4.0 cluster with strict managed table set to true. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-21731?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1684= 3635#comment-16843635 ]=20 Hive QA commented on HIVE-21731: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12969111/HIVE-21731.05.pat= ch {color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified. {color:green}SUCCESS:{color} +1 due to 16057 tests passed Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/17253/test= Report Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17253/co= nsole Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17253/ 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: 12969111 - PreCommit-HIVE-Build > Hive import fails, post upgrade of source 3.0 cluster, to a target 4.0 cl= uster with strict managed table set to true. > -------------------------------------------------------------------------= -------------------------------------------- > > Key: HIVE-21731 > URL: https://issues.apache.org/jira/browse/HIVE-21731 > Project: Hive > Issue Type: Bug > Reporter: mahesh kumar behera > Assignee: mahesh kumar behera > Priority: Major > Labels: pull-request-available > Attachments: HIVE-21731.01.patch, HIVE-21731.02.patch, HIVE-21731= .03.patch, HIVE-21731.04.patch, HIVE-21731.05.patch > > Time Spent: 3h 20m > Remaining Estimate: 0h > > The scenario is=C2=A0 > # Replication policy is set with hive=C2=A0 3.0 source cluster (strict m= anaged table set to false) and hive 4.0 target cluster with strict managed = table set=C2=A0 true. > # User upgrades the 3.0 source cluster to 4.0 cluster using upgrade tool= . > # The upgrade converts all managed tables to acid tables. > # In the next repl dump, user sets hive .repl .dump .include .acid .tabl= es and=C2=A0hive .repl .bootstrap. acid. tables set true triggering bootstr= ap of newly converted ACID tables. > # As the old tables are non-txn tables, dump is not=C2=A0filtering the e= vents even tough bootstrap acid table is set to true. This is causing the r= epl load to fail as the write id is not set in the table object. > # If we ignore the event replay, the bootstrap is failing with dump dire= ctory mismatch error. > The fix should be=C2=A0 > # Ignore dumping the alter table event if bootstrap acid table is set tr= ue and the alter is converting a non-acid table to acid table. > # In case of bootstrap during incremental load, ignore the dump director= y property set in table object. -- This message was sent by Atlassian JIRA (v7.6.3#76005)