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 "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2023/05/09 16:11:00 UTC
[jira] [Created] (IMPALA-12130) Table creation time is not set properly in lineage log for Kudu and Iceberg tables
Zoltán Borók-Nagy created IMPALA-12130:
------------------------------------------
Summary: Table creation time is not set properly in lineage log for Kudu and Iceberg tables
Key: IMPALA-12130
URL: https://issues.apache.org/jira/browse/IMPALA-12130
Project: IMPALA
Issue Type: Bug
Components: Catalog
Reporter: Zoltán Borók-Nagy
For newly created tables, table creation time in the lineage log is set in ClientRequestState::LogLineageRecord():
[https://github.com/apache/impala/blob/9fb1274867a59b467617e6292a54fd1f0bb937ad/be/src/service/client-request-state.cc#L2065]
It uses the TDdlExecResponse object to retrieve the creation time of the table.
For regular filesystem-based tables, creation time is set in CatalogOpExecut.createTable():
[https://github.com/apache/impala/blob/9fb1274867a59b467617e6292a54fd1f0bb937ad/fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java#L3579]
However, Kudu tables are created via createKuduTable(), and Iceberg tables are created via createIcebergTable(), neither of which set creation time and table name of the TDdlExecResponse object.
Because of this bug the lineage log contains incomplete information.
--
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