apache / apache/iceberg-rust

Discussion: Optimize `RollingFileWriter` by closing asynchronously

Open
#1,551 1 comment 0 reactions 0 assignees View on GitHub
enhancement not-stale
Dominant language
Rust
Stars
1.4k
Forks
567
Avg merge
2d 2h
Merged PRs (30d)
93

Description

### Is your feature request related to a problem or challenge?

Reference: https://github.com/apache/iceberg-rust/pull/1547#discussion_r2229405980

When rolling over to a new file, instead of waiting on the current writer to close, we can spawn a thread to improve its efficiency. But we need to be careful about the max parallelism since too many writers or an over-sized buffer can exhaust the memory

### Describe the solution you'd like

_No response_

### Willingness to contribute

None

Contributor guide

Open the contributing guide

Research direction

Start with the RollingFileWriter discussion linked from PR #1547, focusing on rollover behavior and the proposed asynchronous close. Determine how max parallelism and buffer size should be bounded, then define completion criteria that preserve memory safety while improving rollover efficiency.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.