[jira] [Updated] (HIVE-28622) Duplicate Entries in TXN_WRITE_NOTIFICATION_LOG Due to Oracle's Handling of Empty Strings

["Denys Kuzmenko (Jira)" <ji...@apache.org>]

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

Denys Kuzmenko updated HIVE-28622:
----------------------------------
    Fix Version/s: 4.1.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> Duplicate Entries in TXN_WRITE_NOTIFICATION_LOG Due to Oracle's Handling of Empty Strings
> -----------------------------------------------------------------------------------------
>
>                 Key: HIVE-28622
>                 URL: https://issues.apache.org/jira/browse/HIVE-28622
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Subhasis Gorai
>            Assignee: Harshal Patel
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.1.0
>
>
> In Oracle, empty strings ({{{}''{}}}) are treated as {{NULL}} values for both {{VARCHAR2}} and {{CHAR}} data types. This behavior is unique to Oracle and can be confusing, as an empty string is typically considered distinct from {{NULL}} in other databases.
> As a result, the {{TXN_WRITE_NOTIFICATION_LOG}} table receives duplicate entries for a single Hive ACID transaction involving {{MERGE}} statements.
> This discrepancy leads to issues: the {{_files}} and {{_dumpmetadata}} files in a Hive ACID incremental dump will not align if the dump scope includes one or more {{MERGE}} statements. Consequently, the Hive ACID incremental {{LOAD}} fails at the target (DR), blocking subsequent replication executions.



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