[
https://issues.apache.org/jira/browse/HIVE-27926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Saxena resolved HIVE-27926.
---------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
> Iceberg: Allow restricting Iceberg data file reads to table location
> --------------------------------------------------------------------
>
> Key: HIVE-27926
> URL: https://issues.apache.org/jira/browse/HIVE-27926
> Project: Hive
> Issue Type: Sub-task
> Components: Iceberg integration
> Affects Versions: 4.0.0-alpha-2
> Reporter: Janos Kovacs
> Assignee: Ayush Saxena
> Priority: Blocker
> Fix For: 4.0.0
>
>
> As the first quick solution there should be a configuration flag to allow us
> to restrict Iceberg reads to data files located only inside of the table
> locations.
> e.g. with the following definition
> {noformat}
> CREATE EXTERNAL TABLE default.iceloc1 (txt string, secret string)
> STORED BY ICEBERG
> LOCATION '/data/hive/external/iceloc1/'
> TBLPROPERTIES (
> 'external.table.purge'='true',
> 'write.metadata.path'='/data/ice/meta/iceloc1/',
> 'write.data.path'='/data/ice/data/iceloc1/');
> {noformat}
> The restricted location should be
> {noformat}
> /data/hive/external/iceloc1/
> {noformat}
> Note: this configuration should not be enabled by default as this breaks
> Iceberg's functionality storing data files in different locations and would
> only be useful when users use iceberg only as standard external tables with
> meta+data under table location.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
