-
Notifications
You must be signed in to change notification settings - Fork 321
Credential Provider Support #4332
Copy link
Copy link
Open
Labels
area:scanParquet scan / data readingParquet scan / data readingenhancementNew feature or requestNew feature or requestnative_iceberg_compatSpecific to native_iceberg_compat scan typeSpecific to native_iceberg_compat scan typepriority:mediumFunctional bugs, performance regressions, broken featuresFunctional bugs, performance regressions, broken features
Metadata
Metadata
Assignees
Labels
area:scanParquet scan / data readingParquet scan / data readingenhancementNew feature or requestNew feature or requestnative_iceberg_compatSpecific to native_iceberg_compat scan typeSpecific to native_iceberg_compat scan typepriority:mediumFunctional bugs, performance regressions, broken featuresFunctional bugs, performance regressions, broken features
Type
Fields
Give feedbackNo fields configured for issues without a type.
What is the problem the feature request solves?
Comet's scan currently only takes static credentials.
Iceberg-rust already supports a credential hook (AwsCredentialLoad / CustomAwsCredentialLoader in iceberg-storage-opendal). Comet is not wired to use it.
We should expose a pluggable CometCredentialProvider SPI and connect it to that existing hook.
Describe the potential solution
Thread the Java credential provider already in use with Spark into Comet, and make JNI calls when needed to get creds.
Additional context
No response