Attaching DB via URL on Windows leads to "Cannot open file" error
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the failure with the linked DuckdbBugRepro project on Windows, focusing on DuckdbBugRepro.java at the attachDatabaseFromHttpUrl call around line 80. Compare behavior between versions 1.2.2.0 and 1.3.0.0, then verify that attaching the signed HTTP URL no longer treats it as a local file.
Written by the indexing model from the issue text.
Description
When attempting to attach a database via an HTTP URL on Windows, DuckDB seems to interpret the URL as a file and then fails to open it. This issue was introduced between versions 1.2.2.0 and 1.3.0.0. Here is a repo that is able to reproduce the error:
https://github.com/nikammerlaan/duckdb-bug-repro
DuckdbBugRepro > test() FAILED
java.sql.SQLException: IO Error: Cannot open file "http://localhost:56144/test-bucket/database.duckdb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minioadmin%2F20250712%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250712T203631Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=c90c1d82b5c44409343a9b42f5e451304808d81035f1c1af8ef22cef8f9cb951": The system cannot find the path specified.
at org.duckdb.DuckDBNative.duckdb_jdbc_execute(Native Method)
at org.duckdb.DuckDBPreparedStatement.execute(DuckDBPreparedStatement.java:178)
at org.duckdb.DuckDBPreparedStatement.execute(DuckDBPreparedStatement.java:155)
at org.duckdb.DuckDBPreparedStatement.execute(DuckDBPreparedStatement.java:241)
at DuckdbBugRepro.attachDatabaseFromHttpUrl(DuckdbBugRepro.java:80)
at DuckdbBugRepro.test(DuckdbBugRepro.java:25)
- Dominant language
- C++
- Stars
- 127
- Forks
- 80
- Avg merge
- 13h 41m
- Merged PRs (30d)
- 44
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from duckdb/duckdb-java
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
duckdb/duckdb-java#832 · 2 comments ·
-
Native SIGSEGV in DuckDB JDBC when repeatedly executing queries with window functions and LIMIT 0 Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-java#871 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
duckdb/duckdb-java#872 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
duckdb/duckdb-java#837 ·
-
executeBatch()` on a prepared INSERT runs s are ~1–2 orders of magnitude slower than the Appender Open
Difficulty 5/5 Over a week Newbie friendliness 42/100
duckdb/duckdb-java#815 · 1 comment ·
All issues in duckdb/duckdb-java
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·