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 2020/10/02 14:46:00 UTC
[jira] [Assigned] (IMPALA-10209) Iceberg table doesn't set
object_catalog_version for the response object in doGetPartialCatalogObject
[ https://issues.apache.org/jira/browse/IMPALA-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltán Borók-Nagy reassigned IMPALA-10209:
------------------------------------------
Assignee: Zoltán Borók-Nagy
> Iceberg table doesn't set object_catalog_version for the response object in doGetPartialCatalogObject
> -----------------------------------------------------------------------------------------------------
>
> Key: IMPALA-10209
> URL: https://issues.apache.org/jira/browse/IMPALA-10209
> Project: IMPALA
> Issue Type: Bug
> Reporter: Zoltán Borók-Nagy
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Labels: impala-iceberg
>
> Iceberg tables have an underlying hdfs table member. When the IcebergTable object gets a new catalog version it doesn't set the version number for the underlying HdfsTable.
> We use the HdfsTable member to answer CatalogServiceCatalog.doGetPartialCatalogObject() for Iceberg tables, so the response object will always have object_version_number == 0. This leads to various errors and strange behavior as the cache invalidation in local catalog depends on this value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org