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

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

                Author: ASF GitHub Bot
            Created on: 24/Jun/22 22:54
            Start Date: 24/Jun/22 22:54
    Worklog Time Spent: 10m 
      Work Description: cmunkey commented on PR #3365:
URL: https://github.com/apache/hive/pull/3365#issuecomment-1166051272

   I was able to fix the tests.
   The replication unit tests do not really allow updates to occur on the 
replica, this because the two DbTxnHandlers (primary and replica) actually use 
the same Derby database.
   For the purposes of these tests, I can test the same (txnId skew) by doing 
extra updates on the
   primary to force the primary to have larger txnIds than the replica.
   
   




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

    Worklog Id:     (was: 784740)
    Time Spent: 3h 10m  (was: 3h)

> REPL DUMP should filter out OpenXacts and unneeded CommitXact/Abort.
> --------------------------------------------------------------------
>
>                 Key: HIVE-26265
>                 URL: https://issues.apache.org/jira/browse/HIVE-26265
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>            Reporter: francis pang
>            Assignee: francis pang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> REPL DUMP is replication all OpenXacts, even when they are from other non 
> replicated databases. This wastes space in the dump, and ends up opening 
> unneeded transactions during REPL LOAD.
>  
> Add a config property for replication that filters out OpenXact events during 
> REPL DUMP. During REPL LOAD, the txns can be implicitly opened when the 
> ALLOC_WRITE_ID is processed. For CommitTxn and AbortTxn, dump only if WRITE 
> ID was allocated.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to