You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/03/07 08:53:00 UTC
[jira] [Work logged] (HIVE-27123) In PRE_OPTIMIZED_BOOTSTRAP operation, Load side stores dump_execution_id as -1
[ https://issues.apache.org/jira/browse/HIVE-27123?focusedWorklogId=849496&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-849496 ]
ASF GitHub Bot logged work on HIVE-27123:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Mar/23 08:52
Start Date: 07/Mar/23 08:52
Worklog Time Spent: 10m
Work Description: harshal-16 opened a new pull request, #4100:
URL: https://github.com/apache/hive/pull/4100
- Added dump_execution_id in Metadata file which is being picked up by Load operation
Issue Time Tracking
-------------------
Worklog Id: (was: 849496)
Remaining Estimate: 0h
Time Spent: 10m
> In PRE_OPTIMIZED_BOOTSTRAP operation, Load side stores dump_execution_id as -1
> ------------------------------------------------------------------------------
>
> Key: HIVE-27123
> URL: https://issues.apache.org/jira/browse/HIVE-27123
> Project: Hive
> Issue Type: Bug
> Reporter: Harshal Patel
> Assignee: Harshal Patel
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For PRE_OPTIMIZED_BOOSTRAP operation, dump side correctly stores execution ids in replication_metrics but Load side stores dump_execution_id as -1 which should be = execution_id of DUMP operation
--
This message was sent by Atlassian Jira
(v8.20.10#820010)