[
https://issues.apache.org/jira/browse/IMPALA-11545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boglarka Egyed reassigned IMPALA-11545:
---------------------------------------
Assignee: Zoltán Borók-Nagy
> Set option for Iceberg GC_ENABLED
> ---------------------------------
>
> Key: IMPALA-11545
> URL: https://issues.apache.org/jira/browse/IMPALA-11545
> Project: IMPALA
> Issue Type: New Feature
> Reporter: Manish Maheshwari
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Labels: impala-iceberg
>
> Add set property for Iceberg GC_ENABLED (iceberg.gc.enabled) to control
> whether data is dropped or not during drop/truncate table. This will also
> allow users to know what is the default behaviour by querying this set option
> rather than be unaware of what the value is set to. Futher this will also
> allow users to change behaviour if needed in line with spark and hive.
> The way that Iceberg table should behave should be in line with
> [https://github.com/apache/iceberg/issues/4159] and we should ignore the
> `external.table.purge` configuration and document that for iceberg tables
> `external.table.purge` does not apply. Essentailly iceberg tables are managed
> tables even though called external due to the Hive 3 naming conventions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
