You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Abhishek Rawat (Jira)" <ji...@apache.org> on 2026/02/21 16:55:00 UTC
[jira] [Updated] (IMPALA-13599) Reduce ALTER_PARTITION events fired from Impala
[ https://issues.apache.org/jira/browse/IMPALA-13599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhishek Rawat updated IMPALA-13599:
------------------------------------
Priority: Critical (was: Major)
> Reduce ALTER_PARTITION events fired from Impala
> -----------------------------------------------
>
> Key: IMPALA-13599
> URL: https://issues.apache.org/jira/browse/IMPALA-13599
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Reporter: Sai Hemanth Gantasala
> Assignee: Sai Hemanth Gantasala
> Priority: Critical
> Fix For: Impala 4.5.1
>
>
> There are a couple of APIs in Impala that fire ALTER_PARTITION for each partition.
> {code:java}
> Alter table foo set cached/uncached;
> Drop stats table_name;{code}
> These table-level operations are calling HMS APIs alter_partition() thousands times if there are an equal number of partitions. The side effect is that it leads to thousands of alter partition events.
> We should optimize to call alter_partitions() HMS API only once for these operations and bulk update the partitions.
> P.S: HIVE-27746 - We can ultimately leverage this to have a single alter_partitions event that can help the event processor catch up with lag quickly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org