[
https://issues.apache.org/jira/browse/HIVE-28976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Kuzmenko updated HIVE-28976:
----------------------------------
Component/s: Standalone Metastore
> 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, Standalone Metastore
> Reporter: Harshal Patel
> Assignee: Harshal Patel
> Priority: Major
> Labels: pull-request-available, replication
> Fix For: 4.1.0
>
>
> 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)
