badalprasadsingh opened a new issue, #1189: URL: https://github.com/apache/iceberg-go/issues/1189
### Apache Iceberg version main (development) ### Please describe the bug š When a SQL catalog is loaded with S3 properties such as `s3.endpoint`, `s3.access-key-id`, `s3.secret-access-key`, `s3.region`, the very first `CreateTable` succeeds, but the next `CommitTable` (any append, schema change, etc.) fails to upload the new `*.metadata.json`. Data file uploads (parquet, manifests, manifest list) succeed because they go through an IO that was built from the catalog props (using `LoadTable`'s `io.LoadFSFunc(c.props, ā¦)`). Only the final `metadata.json` upload at commit time uses the wrong IO. **Proposed Solution** Merge `c.props` (catalog-level properties) into the IO props passed to `WriteMetadata`, with `staged.Properties()` taking precedence so per- table overrides (e.g. `write.metadata.compression-codec`) still win. This is the same precedence `CreateStagedTable` already uses for the initial create path. **Contribution** Iād be happy to work on this issue. Please feel free to assign this issue to me and I can prepare a PR implementing it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
