You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ádám Szita (Jira)" <ji...@apache.org> on 2022/02/04 14:26:00 UTC
[jira] [Resolved] (HIVE-25772) Use ClusteredWriter when writing to Iceberg tables
[ https://issues.apache.org/jira/browse/HIVE-25772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ádám Szita resolved HIVE-25772.
-------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Pushed to master. Thanks for the review [~Marton Bod]!
> Use ClusteredWriter when writing to Iceberg tables
> --------------------------------------------------
>
> Key: HIVE-25772
> URL: https://issues.apache.org/jira/browse/HIVE-25772
> Project: Hive
> Issue Type: Improvement
> Reporter: Ádám Szita
> Assignee: Ádám Szita
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Currently Hive relies on PartitionedFanoutWriter to write records to Iceberg tables. This has a big disadvantage when it comes to writing many-many partitions, as it keeps a file handle open to each of the partitions.
> For some file systems like S3, there can be a big resource waste due to keeping bytebuffers for each of the handles, that may result in OOM scenarios.
> ClusteredWriter will only write one file at a time, and will not keep other file handles open, but it will expect that the input data is sorted by partition keys.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)