Skip to content

Conversation

@devinrsmith
Copy link
Contributor

If an S3AsyncClient has been used from S3FileIO and the analytics accelerator is disabled (is disabled by default), the S3FileIO may throw an exception during closing if the analytics accelerator is not on the classpath.

Closes #13133

If an S3AsyncClient has been used from S3FileIO and the analytics accelerator is disabled (is disabled by default), the S3FileIO may throw an exception during closing if the analytics accelerator is not on the classpath.

Closes apache#13133
@github-actions github-actions bot added the AWS label May 23, 2025
@nastra
Copy link
Contributor

nastra commented May 23, 2025

@SanjayMarreddi since you were working on #12299 can you please double-check this change here?

Copy link
Contributor

@SanjayMarreddi SanjayMarreddi left a comment

Choose a reason for hiding this comment

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

Looks good to me, thanks for this fix.

@SanjayMarreddi
Copy link
Contributor

Also want to highlight the relevant clean up PR similar to this change here: #12891

@nastra nastra merged commit 793f6cd into apache:main May 23, 2025
42 checks passed
devendra-nr pushed a commit to devendra-nr/iceberg that referenced this pull request Dec 8, 2025
If an S3AsyncClient has been used from S3FileIO and the analytics accelerator is disabled (is disabled by default), the S3FileIO may throw an exception during closing if the analytics accelerator is not on the classpath.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AWS: Closing S3FileIO can result in ClassNotFoundException

4 participants