[jira] [Created] (IMPALA-12636) When enable_sync_to_latest_event_on_ddls flag is enabled, truncate table operation modifies cache in-place

["Sai Hemanth Gantasala (Jira)" <ji...@apache.org>]

Sai Hemanth Gantasala created IMPALA-12636:
----------------------------------------------

             Summary: When enable_sync_to_latest_event_on_ddls flag is enabled, truncate table operation modifies cache in-place
                 Key: IMPALA-12636
                 URL: https://issues.apache.org/jira/browse/IMPALA-12636
             Project: IMPALA
          Issue Type: Task
          Components: Catalog
            Reporter: Sai Hemanth Gantasala
            Assignee: Sai Hemanth Gantasala


IMPALA-10976 modifies catalogD's cache using MetaStoreEventsProcessor for all DDLs/DMLs when the 'enable_sync_to_latest_event_on_ddls' flag is enabled.

Although, there is an exception. For the truncate table operation executed via Impala, if the table is not replicated, then Impala doesn't use the truncate_table() API of HMS and hence the alter table event generated as a part of the truncate operation does not indicate that the table is truncated. Even though we truncate table stats and col stats as a part of the truncate operation, if the stats are not computed previously, then the event processor has no way to find out that the table is truncated.

Truncate operation via HMS will generate an alter table event and the alter table event has a field 'isTruncateOp' set to true which indicates that the alter table event is generated due to truncate table operation.



--
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