pavibhai opened a new pull request, #1932: URL: https://github.com/apache/polaris/pull/1932
**Summary** * Added support for s3a scheme when referring to paths on AWS S3 * scheme is ignored when comparing s3 and s3a paths for e.g. in overlap checks * Tests have been added * Some tests have been modified to run parameterized both for `s3` and `s3a` **Motivation** In the absence of this change, for tables involving `S3AFileSystem` the default scheme of `s3a` was used in the Iceberg metadata files. When you try to register this table it fails as `s3a` is not a valid scheme in Apache Polaris As a workaround we had to at a minimum update the snapshot file to change the table location from `s3a://` to `s3://` for the table to be registered with Polaris **Desired Behavior** We should be able to treat both `s3://` and `s3a://` as valid AWS S3 references -- 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: issues-unsubscr...@polaris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
