-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure ADLS Gen2 with HNS: Unable to delta_scan FQDN abfss URL #71
Comments
ah, with AZURE_LOG_LEVEL=verbose I can see that the first HEAD request sent (by the Delta kernel?) uses the wrong syntax when the abfss URL uses the FQDN:
Using the "shorthand" abfss syntax, the HEAD request uses the correct format URL:
So, now to figure out how that happened. |
After building the delta extension with my fork of the duckdb_azure extension it looks like this problem is fixed. |
Will close this one as it is fixed on nightlies now and scheduled for release in upcoming duckdb v1.1.0 release |
Using a FQDN HNS hostname causes an error.
For example (where the secret has already been configured for
mystorageaccount
), this works:But this fails with a "bad request" error:
I think the code for determining the
bucket
variable needs to be updated (around line 173)?Also the "azure_endpoint" is being hard-coded to
https://" + account_name + ".**blob**.core.windows.net/
instead of.dfs.
. I guess theendpoint
builder option does not need to be set when a FQDN is used? or, if endpoint is empty or null then use the value of the duckdbazure_endpoint
variable? (select current_setting('azure_endpoint');
)I'm having trouble setting up my local environment for developing and testing the extension myself so this is currently just guesswork.
The text was updated successfully, but these errors were encountered: