[
https://issues.apache.org/jira/browse/IMPALA-8831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934386#comment-16934386
]
Csaba Ringhofer commented on IMPALA-8831:
-----------------------------------------
I think that the main modification will be to start a transaction and lock the
table (in most cases with an exclusive lock).
Hive decides the type of lock needed depending on the ALTER TABLE's type here:
https://github.infra.cloudera.com/CDH/hive/blob/cd21beb361785db8a8eda40be56087e06c3554c1/ql/src/java/org/apache/hadoop/hive/ql/hooks/WriteEntity.java#L198
The only command that need to call a different API for transactional tables are
the (manual) updating of stats. The need a writeId + validWriteID list in the
API call.
> Modify ALTER TABLE to handle insert-only transactional tables
> -------------------------------------------------------------
>
> Key: IMPALA-8831
> URL: https://issues.apache.org/jira/browse/IMPALA-8831
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 3.3.0
> Reporter: Gabor Kaszab
> Priority: Critical
> Labels: ACID, impala-acid
>
> I haven't made much investigation on this topic so the first part of this
> Jira is to do a research which ALTER TABLE commands are affected.
> Once we have a list of those then the second part is to modify them to handle
> transactional tables properly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
