You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to replicate the issue (preferably on an apple silicon machine. requires docker):
clone repo above
run ./extension_issue_1.2.0.sh
Output on v1.1.3
[jbang] Resolving dependencies...
[jbang] org.duckdb:duckdb_jdbc:1.1.3
[jbang] Dependencies resolved
[jbang] Building jar for ExtensionIssueDemo.java...
getting connection
Executing query
linux_arm64
done executing query
Output on v1.2.0
[jbang] Resolving dependencies...
[jbang] org.duckdb:duckdb_jdbc:1.2.0
[jbang] Dependencies resolved
[jbang] Building jar for ExtensionIssueDemo.java...
getting connection
Executing query
linux_arm64_gcc4
Exception in thread "main" java.sql.SQLException: java.sql.SQLException: HTTP Error: Failed to download extension "httpfs" at URL "http://extensions.duckdb.org/v1.2.0/linux_arm64_gcc4/httpfs.duckdb_extension.gz" (HTTP 403)
Extension "httpfs" is an existing extension.
For more info, visit https://duckdb.org/docs/extensions/troubleshooting/?version=v1.2.0&platform=linux_arm64_gcc4&extension=httpfs
at org.duckdb.DuckDBPreparedStatement.prepare(DuckDBPreparedStatement.java:121)
at org.duckdb.DuckDBPreparedStatement.execute(DuckDBPreparedStatement.java:201)
at ExtensionIssueDemo.main(ExtensionIssueDemo.java:26)
Caused by: java.sql.SQLException: HTTP Error: Failed to download extension "httpfs" at URL "http://extensions.duckdb.org/v1.2.0/linux_arm64_gcc4/httpfs.duckdb_extension.gz" (HTTP 403)
Extension "httpfs" is an existing extension.
For more info, visit https://duckdb.org/docs/extensions/troubleshooting/?version=v1.2.0&platform=linux_arm64_gcc4&extension=httpfs
at org.duckdb.DuckDBNative.duckdb_jdbc_prepare(Native Method)
at org.duckdb.DuckDBPreparedStatement.prepare(DuckDBPreparedStatement.java:115)
... 2 more
The text was updated successfully, but these errors were encountered:
I'm running into this as well. The information above is accurate.
The duckdb CLI distribution loads the aws extension just fine as linux_arm64 however the binary in the JDBC driver wants to use linux_arm64_gcc4.
I tried symlink'ing to try to work around the issue, but the extensions are incompatible. DuckDB saw the symlink but refused to load the incompatible version.
Extensions are failing to load when run on a linux_arm64 environment.
This seems to be happening only in the duckdb_jdbc driver. Duckdb CLI does not have this issue.
Seems to be related to the output of "pragma platform" returning "linux_arm64" in v1.1.3 and "linux_arm64_gcc4" in v1.2.0
Potentially related to this change: https://github.com/duckdb/duckdb-java/pull/106/files#diff-bdee261ab427fca8a87834d14e7706a57244a4959edd41839a00799608932571R29
MRE to demonstrate issue: https://github.com/juja0/duckdb_deadlock
Steps to replicate the issue (preferably on an apple silicon machine. requires docker):
Output on v1.1.3
Output on v1.2.0
The text was updated successfully, but these errors were encountered: