AWS S3 Support #31
Open
AWS S3 Support #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g data and metadata.
|
Thanks @Ralnoc , but I don't think we want to add the Hadoop dependencies here. If we want to add S3 support, it should be through |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for AWS S3 as a Iceberg table location through s3a:// as a filesystem to store Iceberg data and metadata.
Included are updates to pre-package the core-site.xml in the correct location so that AWS IAM Role policies will work, regardless to if they are pulling from an EC2 instance IAM Profile, Environment Variables, a credential file or Kubernetes IRSA Web Token authentication.