You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Denys Kuzmenko (Jira)" <ji...@apache.org> on 2020/12/03 16:46:00 UTC

[jira] [Comment Edited] (HIVE-24482) Advance write Id during AlterTableAddConstraint DDL

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

Denys Kuzmenko edited comment on HIVE-24482 at 12/3/20, 4:45 PM:
-----------------------------------------------------------------

Does it mean that AlterTableAddConstraint on HMS1 is going to invalidate ValidWriteIdList in the CachedStore on HMS2 and following select statement from this table should go db directly?


was (Author: dkuzmenko):
Does it mean that AlterTableAddConstraint on HMS1 is going to invalidate ValidWriteIdList in the CachedStore on HMS 2 and following select statement from this table should go db directly?

> Advance write Id during AlterTableAddConstraint DDL
> ---------------------------------------------------
>
>                 Key: HIVE-24482
>                 URL: https://issues.apache.org/jira/browse/HIVE-24482
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Kishen Das
>            Assignee: Kishen Das
>            Priority: Major
>
> For AlterTableAddConstraint related DDL tasks, although we might be advancing the write ID, looks like it's not updated correctly during the Analyzer phase. 



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