Currently, S3PinotFS implementation falls back to initialize credential using DefaultCredentialsProvider when the access key and secret is not provided by the pinot config. In this way, we allow users to set env variables like AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
For ADLS Gen2 Pinot FS, we expect users to pass accessKey and accountName via pinot config. We should use default credential provider when those information is not given.
Currently, S3PinotFS implementation falls back to initialize credential using
DefaultCredentialsProvider
when the access key and secret is not provided by the pinot config. In this way, we allow users to set env variables likeAWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
.For ADLS Gen2 Pinot FS, we expect users to pass
accessKey
andaccountName
via pinot config. We should use default credential provider when those information is not given.Some references to look:
https://learn.microsoft.com/en-us/azure/storage/blobs/storage-quickstart-blobs-java?tabs=powershell%2Cmanaged-identity%2Croles-azure-portal%2Csign-in-azure-cli https://blog.jongallant.com/2021/08/azure-identity-101/