[
https://issues.apache.org/jira/browse/IMPALA-11710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730952#comment-17730952
]
Gabor Kaszab commented on IMPALA-11710:
---------------------------------------
Ran into the same with a different table property. For the record let me add
the repro steps:
create table tmp_ice (i int, s string) stored as iceberg tblproperties
('external.table.purge'='false');
alter table tmp_ice set tblproperties('external.table.purge'='true');
now if you call {{describe formatted tmp_ice;}} it's set to true as expected.
insert into tmp_ice values (1, "str1");
But if you for instance insert a row into a table it's set to false again.
(checked in {{describe formatted}} and also {{{}show create table{}}})
> Table properties are not updated in Iceberg metadata files
> ----------------------------------------------------------
>
> Key: IMPALA-11710
> URL: https://issues.apache.org/jira/browse/IMPALA-11710
> Project: IMPALA
> Issue Type: Bug
> Reporter: Noemi Pap-Takacs
> Priority: Major
> Labels: impala-iceberg
>
> This issue occurs in true external Hive Catalog tables.
> Iceberg stores the default file format in a table property called
> 'write.format.default'. HMS also stores this value loaded from the Iceberg
> metadata json file.
> However, when this table property is altered through Impala, it is only
> changed in HMS, but does not update the Iceberg snapshot. When the table data
> is reloaded from Iceberg metadata, the old value will appear in HMS and the
> change is lost.
> This bug does not affect table properties that are not stored in Iceberg,
> because they will not be reloaded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
