Skip to content

[Iceberg AddFiles] Use thread pool to process incoming datafiles#38018

Merged
ahmedabu98 merged 6 commits intoapache:masterfrom
ahmedabu98:add-files-perf
Apr 1, 2026
Merged

[Iceberg AddFiles] Use thread pool to process incoming datafiles#38018
ahmedabu98 merged 6 commits intoapache:masterfrom
ahmedabu98:add-files-perf

Conversation

@ahmedabu98
Copy link
Copy Markdown
Contributor

@ahmedabu98 ahmedabu98 commented Mar 31, 2026

Improve performance by processing incoming files using a thread pool, allowing a single worker to process files in parallel.

Fixes #38012

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the performance of the Iceberg AddFiles operation by introducing parallel processing capabilities. By leveraging a thread pool within the ConvertToDataFile DoFn, the system can now concurrently handle multiple incoming data files, thereby reducing bottlenecks associated with sequential file I/O and metadata operations. This change optimizes resource utilization and accelerates the overall data ingestion process into Iceberg tables.

Highlights

  • Asynchronous File Processing: Implemented asynchronous processing of incoming data files within the ConvertToDataFile DoFn to improve performance.
  • Thread Pool Integration: Introduced an ExecutorService (thread pool) to parallelize latency-bound operations such as file I/O, catalog lookups, and metadata inference for multiple files concurrently within a single DoFn instance.
  • DoFn Lifecycle Management: Refactored the ProcessElement method to submit file processing tasks to the thread pool and added a FinishBundle method to await the completion of all tasks in the current bundle and safely emit results.
  • Result Encapsulation: Created a new ProcessResult internal class to encapsulate the outcome of each file's processing, including the SerializableDataFile or any error Row, along with its timestamp and window.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@chamikaramj chamikaramj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

private static final int MAX_READERS = 10;
private static final Semaphore ACTIVE_READERS = new Semaphore(MAX_READERS);
// Number of parallel threads processing incoming files
private static final int THREAD_POOL_SIZE = 10;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably we should do some experimentation to pick a reasonable default here or base this on similar optimizations done for other I/Os.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doing some experiments now

@github-actions
Copy link
Copy Markdown
Contributor

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

Copy link
Copy Markdown
Contributor

@chamikaramj chamikaramj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. LGTM.

@ahmedabu98 ahmedabu98 merged commit ee02db8 into apache:master Apr 1, 2026
19 checks passed
@ahmedabu98 ahmedabu98 deleted the add-files-perf branch April 1, 2026 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Improve performance of the Iceberg AddFiles transform

2 participants