-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: DH-18149: Simplified passing s3 instructions for iceberg writing #6668
base: main
Are you sure you want to change the base?
Conversation
extensions/iceberg/src/main/java/io/deephaven/iceberg/util/IcebergTableAdapter.java
Outdated
Show resolved
Hide resolved
...nsions/iceberg/s3/src/test/java/io/deephaven/iceberg/util/TableParquetWriterOptionsTest.java
Outdated
Show resolved
Hide resolved
@NotNull final DataInstructionsProviderLoader dataInstructionsProvider) { | ||
super(tableAdapter, instructions, dataInstructionsProvider); | ||
@NotNull final DataInstructionsProviderLoader dataInstructionsProvider, | ||
@NotNull final String tableLocationUriScheme) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is technically a breaking change. One of the reasons why I don't like exposing this as a public interface to consumers. Ditto wrt Base layout and KV layout.
Practically, I think we should make this package private. I know that DHE constructs these directly though, so we need to audit how / why they are using it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. I have made the change non-breaking and created a separate ticket (DH-18831) for investigating into the DHE Iceberg construction logic.
JIRA ticket: https://deephaven.atlassian.net/browse/DH-18149
Description:
Previously, users had to provide the S3 configuration (username, password, region, etc.) in two places:
With this PR, if the S3 configuration is not passed when constructing the table writer, it will automatically inherit the configuration from the catalog properties. This change aligns with the existing pattern used for reading iceberg tables.