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 2023/02/01 04:38:00 UTC

[jira] [Commented] (HIVE-26934) Update TXN_WRITE_NOTIFICATION_LOG table schema to make WNL_TABLE width consistent with other tables

    [ https://issues.apache.org/jira/browse/HIVE-26934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682844#comment-17682844 ] 

Harshal Patel commented on HIVE-26934:
--------------------------------------

All changes are already in place. So no update is required

> Update TXN_WRITE_NOTIFICATION_LOG table schema to make WNL_TABLE width consistent with other tables
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-26934
>                 URL: https://issues.apache.org/jira/browse/HIVE-26934
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Harshal Patel
>            Assignee: Harshal Patel
>            Priority: Major
>
> * TXN_WRITE_NOTIFICATION_LOG has table as varchar(128) and in other metastore tables, hive table type is varchar(256).
>  * So, if user creates hive table with name > 128 characters then during Incremental Repl Load operation, EVENT_COMMIT_TXN event reads table name from the TXN_WRITE_NOTIFICATION_LOG table and it only gets first 128 characters and eventually creates wrong file path



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