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 "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/05/16 10:07:00 UTC

[jira] [Commented] (IMPALA-12130) Table creation time is not set properly in lineage log for Kudu and Iceberg tables

    [ https://issues.apache.org/jira/browse/IMPALA-12130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723079#comment-17723079 ] 

ASF subversion and git services commented on IMPALA-12130:
----------------------------------------------------------

Commit 650758ffd93b326e3bede4822d4d716d7b2aa852 in impala's branch refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=650758ffd ]

IMPALA-12130: Table creation time is not set properly in lineage log for Kudu and Iceberg tables

For CTAS statements that create Kudu/Iceberg tables the lineage log
was incomplete as it missed the table creation time of the newly
created table. This information was missing because in CatalogOpExecutor
createKuduTable() / createIcebergTable() did not set it in the
TDdlExecResponse object. This patch adds the missing information.

Testing
 * e2e test

Change-Id: I6938938b1834809d5197a748c171e9a09e13906a
Reviewed-on: http://gerrit.cloudera.org:8080/19868
Tested-by: Impala Public Jenkins <im...@cloudera.com>
Reviewed-by: Gabor Kaszab <ga...@cloudera.com>


> 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
>            Assignee: Zoltán Borók-Nagy
>            Priority: Major
>
> 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