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

Posted to issues@hive.apache.org by "Peter Vary (Jira)" <ji...@apache.org> on 2021/07/30 05:34:00 UTC

[jira] [Commented] (HIVE-25407) [Hive] Investigate why advancing the Write ID not working for some DDLs and fix it, if appropriate

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

Peter Vary commented on HIVE-25407:
-----------------------------------

We probably don't want to advance the writeId, especially for compactions, where there are no changes in the data. Don't forget that the materialised view handling depends on the writeId to decide if the view data should be used / refreshed or not. If we add unnecessary writeIds we start to cause performance issues with materialised views above the table.

CC: [~klcopp]

> [Hive] Investigate why advancing the Write ID not working for some DDLs and fix it, if appropriate
> --------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-25407
>                 URL: https://issues.apache.org/jira/browse/HIVE-25407
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Kishen Das
>            Priority: Major
>
> Below DDLs should be investigated separately on why the advancing the write ID is not working for transactional tables, even after adding the logic to advance the write ID. 
>  * ALTER TABLE SET PARTITION SPEC 
>  * ALTER TABLE  UNSET SERDEPROPERTIES 
>  * ALTER TABLE COMPACT 
>  * ALTER TABLE SKEWED BY
>  * ALTER TABLE SET SKEWED LOCATION



--
This message was sent by Atlassian Jira
(v8.3.4#803005)