karuppayya opened a new issue, #4245: URL: https://github.com/apache/datafusion-comet/issues/4245
### What is the problem the feature request solves? Follow-up to #4212 / #4213. #4213 added support for mapping `ProfileCredentialsProvider` to the AWS profile credential chain in the native `object_store`-based S3 reader, but it does not currently honor the Hadoop S3A configuration options: - `fs.s3a.auth.profile.name` — selects the named profile to load - `fs.s3a.auth.profile.file` — points to an alternate AWS credentials file These are recognized by Hadoop's `org.apache.hadoop.fs.s3a.auth.ProfileAWSCredentialsProvider` (introduced in Hadoop 3.4.2). Per discussion on #4213 with @parthchandra, the native side should resolve these configs itself (similar to how `AssumedRoleCredentialProvider` and `SimpleAWSCredentialsProvider` already do), so the behavior is independent of the user's bundled Hadoop version. ### Describe the potential solution Read `fs.s3a.auth.profile.name` / `fs.s3a.auth.profile.file` (with bucket-scoped overrides) in `build_aws_credential_provider_metadata` and forward them to `ProfileFileCredentialsProvider::builder()` via `.profile_name(...)` and `.profile_files(ProfileFiles::builder().with_file(Credentials, ...).build())`. ### Additional context - Original feature: #4213 - Discussion: https://github.com/apache/datafusion-comet/pull/4213#issuecomment-4381552760 -- 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]
