[
https://issues.apache.org/jira/browse/IMPALA-12719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808483#comment-17808483
]
ASF subversion and git services commented on IMPALA-12719:
----------------------------------------------------------
Commit 526d6eb68f202c5172d608f661979a40a92c2261 in impala's branch
refs/heads/master from Sai Hemanth Gantasala
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=526d6eb68 ]
IMPALA-12719: Reload filemetadata for AlterTable event of type truncate
When the event processor receives an alter table event and the event
type is of truncate operation currently file metadata is not reloaded.
This patch addresses this issue, where the alter table event type is
verified if it's a truncate operation and then reload the file metadata
accordingly.
Note: Alter table event for an external table generated by the truncate
operation from Impala cannot be identified if it's a truncate op or not
This becomes an issue in multi cluster Impala environments where events
generated from one impala cluster is consumed by other impala clusters.
Truncate operations in Impala on replicated tables will generated alter
event with 'isTruncateOp' field set to true.
Testing:
Added an end-to-end test to verify whether file metadata is reloaded
for the above scenario.
Change-Id: I53bb80c294623eec7c79d9f30f410771386c6b75
Reviewed-on: http://gerrit.cloudera.org:8080/20887
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Reload file metadata for truncate op in metastore
> -------------------------------------------------
>
> Key: IMPALA-12719
> URL: https://issues.apache.org/jira/browse/IMPALA-12719
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 4.3.0
> Reporter: Sai Hemanth Gantasala
> Assignee: Sai Hemanth Gantasala
> Priority: Major
>
> 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.
> After IMPALA-11534, we don't reload file metadata for every trivial alter
> table operation. This Jira tracks the issue to verify that file metadata is
> reloaded in the event processor of CatalogD when the alter table event from
> HMS is due to a truncate operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
