You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Harshal Patel (Jira)" <ji...@apache.org> on 2025/06/05 06:38:00 UTC

[jira] [Updated] (HIVE-28976) Enhance Commit message in notification_log to correctly filter events during incremental replication

     [ https://issues.apache.org/jira/browse/HIVE-28976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harshal Patel updated HIVE-28976:
---------------------------------
    Status: Patch Available  (was: In Progress)

> Enhance Commit message in notification_log to correctly filter events during incremental replication
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-28976
>                 URL: https://issues.apache.org/jira/browse/HIVE-28976
>             Project: Hive
>          Issue Type: Bug
>          Components: repl
>            Reporter: Harshal Patel
>            Assignee: Harshal Patel
>            Priority: Major
>              Labels: replication
>
> If user adds {{hive.repl.filter.transactions}} parameter then we are relying on txn_write_notification_log table to figure out whether Commit event is associated with read / write operation
> But that doesn’t work in case of truncate / DDLDescWithWriteId operations
> so to correctly filter out commit events during dump operation, we need some way to identify it
> For that we need to update message for commit event in notification_log table



--
This message was sent by Atlassian Jira
(v8.20.10#820010)