[
https://issues.apache.org/jira/browse/IMPALA-13245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boglarka Egyed reassigned IMPALA-13245:
---------------------------------------
Assignee: Noémi Pap-Takács
> Table properties in HMS and Iceberg metadata do not align
> ---------------------------------------------------------
>
> Key: IMPALA-13245
> URL: https://issues.apache.org/jira/browse/IMPALA-13245
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend, Test
> Reporter: Noémi Pap-Takács
> Assignee: Noémi Pap-Takács
> Priority: Major
> Labels: impala-iceberg
>
> Some Iceberg test tables in 'functional_parquet' used in Planner tests are
> missing some Iceberg table properties in the Iceberg metadata queried through
> IcebergApiTable, even though the properties are set in HMS (they show up in
> the impala-shell after issuing a 'DESCRIBE FORMATTED' command). Examples
> include: 'write.delete.mode', 'write.update.mode', 'write.merge.mode'
> This causes different behavior depending on where we get the metadata in the
> code.
> I tried to reproduce the issue creating Iceberg tables with Impala but most
> table properties were the same in HMS and Iceberg. E.g. 'write.delete.mode',
> etc. always defaulted to 'merge-on-read' showing up both in HMS and the
> Iceberg metadata. However, the test tables used in Planner tests were created
> with data-load, which could be an explanation.
> Another issue is that when we alter a V1 to V2 by setting
> 'format-version'='2', the table does become a V2 table, but the
> 'format-version' property is not displayed in HMS.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
