dwsmith1983 commented on issue #6605: URL: https://github.com/apache/datafusion-comet/issues/6605#issuecomment-6289487081
Where each item stands, for closing this with #7127. #6059 moved Azure credential resolution to the driver: `AbfsAuthResolver` builds hadoop-azure's own `AbfsConfiguration` from the URL's authority and calls `getPasswordString`, `getTokenProviderClass` and `getTokenProvider`. The native store now reads only the global keys the driver sends. `AbfsAuthParitySuite` checks each case against the real `AzureBlobFileSystem`, pinned per hadoop-azure version in `abfs-auth-parity/expected-<version>.json`. 1. Container-scoped OAuth keys: covered by #6059. Parity cases `oauth-clientcreds-container-secret`, `oauth-msi-container-tenant`, `oauth-wi-container-token-file`, `cal-sas-container-fixed-token` and `cal-container-oauth-endpoint`, which resolve the container's principal on 3.4.2 and the account's on 3.4.1. 2. Fabric hosts: covered by #6059 by construction. The native endpoint-suffix list is gone, and Hadoop looks keys up under the URL's own authority. There is no Fabric parity case. 3. Account-scoped key forms: covered by #6059. A port in the account is tested (`uri-port-in-account`, `cal-port-key-matches`, `cal-port-key-missing`). The other host-suffix and short `<key>.<account>` forms follow from Hadoop doing the lookup; no case pins them directly. 4. Credential provider stores: covered by #6059. The `cp-jceks-*` cases, including a keystore value winning over a clear-text key. 5. OAuth provider class guard: covered by #6059. `oauth-no-provider-type` and the guard cases fail the way Hadoop does on every version. 6. Error text: #7127. -- 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]
