Skip to content

Comments

[IcebergIO] Don't prematurely close FileIO#37626

Merged
ahmedabu98 merged 1 commit intoapache:masterfrom
ahmedabu98:keep_fileio_open
Feb 18, 2026
Merged

[IcebergIO] Don't prematurely close FileIO#37626
ahmedabu98 merged 1 commit intoapache:masterfrom
ahmedabu98:keep_fileio_open

Conversation

@ahmedabu98
Copy link
Contributor

Was leading to some S3FileIO failures due to connection pool closing prematurely

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @ahmedabu98, 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 addresses a critical issue where FileIO resources were being closed prematurely, leading to S3FileIO failures. The change ensures that the FileIO instance, which manages underlying I/O resources like S3 connection pools, remains open for the duration required by the Table object, thereby improving the stability and reliability of Iceberg I/O operations.

Highlights

  • Resource Management: Prevented the premature closing of FileIO instances by removing an unnecessary try-with-resources block.
  • S3 Stability: Resolved S3FileIO failures that were occurring due to connection pool issues caused by FileIO being closed too early.

🧠 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.

Changelog
  • sdks/java/io/iceberg/src/main/java/org/apache/beam/sdk/io/iceberg/ReadUtils.java
    • Removed the import statement for org.apache.iceberg.io.FileIO as it is no longer explicitly used in a try-with-resources block.
    • Refactored the createReader method to remove the try-with-resources block around table.io(), preventing the premature closing of the FileIO instance.
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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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.

@ahmedabu98 ahmedabu98 added this to the 2.72.0 Release milestone Feb 17, 2026
@github-actions
Copy link
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
Contributor

@Abacn Abacn left a comment

Choose a reason for hiding this comment

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

Sounds like another occurrence of #36438. Shall we do a survey to confirm all FileIO operations are covered?

@ahmedabu98
Copy link
Contributor Author

Correct, it's along the same lines. Just double checked and I think this is the only other spot that closed prematurely.

@github-actions
Copy link
Contributor

Assigning reviewers:

R: @Abacn for label java.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

@ahmedabu98 ahmedabu98 merged commit 1ee2c71 into apache:master Feb 18, 2026
22 of 23 checks passed
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.

2 participants