Failure to auto load httpfs extension after upgrading to 1.5.*
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Start with the Java snippet using the DuckDB JDBC connection and the SET home_directory, secret_directory, extension_directory, and temp_directory statements. Reproduce it in AWS Lambda ARM64 with DuckDB 1.5.* and compare it with 1.4.4.0; done means the httpfs extension loads automatically and CREATE SECRET succeeds without the home-directory error.
Written by the indexing model from the issue text.
Description
After updating to 1.5.0.0 (and newer) versions, I'm seeing the following error:
org.jooq.exception.DataAccessException: SQL [CREATE SECRET s3_credentials (
TYPE S3,
PROVIDER config,
KEY_ID '....',
SECRET '....',
REGION 'us-west-2'
);
]; Extension Autoloading Error: An error occurred while trying to automatically install the required extension 'httpfs':
Can't find the home directory at ''
Specify a home directory using the SET home_directory='/path/to/dir' option.
This happens when I run my code in AWS Lambda ARM64, but not when running on my machine.
Version 1.4.4.0 and earlier work fine.
Snippet that triggers the issue (when running on AWS Lambda).
final var conn = (DuckDBConnection) DriverManager.getConnection("jdbc:duckdb:");
final var config = new DefaultConfiguration().set(conn).set(SQLDialect.DUCKDB);
final var context = DSL.using(config);
context.execute("""
SET home_directory='/tmp/.duckdb';
SET secret_directory='/tmp/.duckdb/sec';
SET extension_directory='/tmp/.duckdb/ext';
SET temp_directory='/tmp';
SET TimeZone='UTC';
""");
context.execute("""
CREATE SECRET s3_credentials (
TYPE S3,
PROVIDER config,
KEY_ID ?,
SECRET ?,
REGION ?
);
""", DSL.inline(accessKey), DSL.inline(secretKey), DSL.inline(region));
- Dominant language
- C++
- Stars
- 127
- Forks
- 81
- Avg merge
- 7h 57m
- Merged PRs (30d)
- 38
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 ·
Maintainers usually reply within 1 day
-
Native SIGSEGV in DuckDB JDBC when repeatedly executing queries with window functions and LIMIT 0Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-java#871 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
duckdb/duckdb-java#872 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
duckdb/duckdb-java#837 ·
Maintainers usually reply within 1 day
-
executeBatch()` on a prepared INSERT runs s are ~1–2 orders of magnitude slower than the AppenderOpen
Difficulty 5/5 Over a week Newbie friendliness 42/100
duckdb/duckdb-java#815 · 1 comment ·
Maintainers usually reply within 1 day
All issues in duckdb/duckdb-java
Similar issues
-
bug chart-audit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
HasBacktrace Priority-Critical
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
azerothcore/azerothcore-wotlk#27921 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
yhirose/cpp-peglib#344 ·