Skip to content

DuckLake options override fix #287

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

staticlibs
Copy link
Collaborator

With the changes introduced in #276 the jdbc:duckdb:ducklake:... URLs have the special handling: jdbc_pin_db and jdbc_stream_results options are applied to them automatically. This behaviour was supposed to be overridable with URL or Properties but by mistake incorrect method was used for override check. And as DuckLake is still not available in the main branch, there is no test coverage for this and the problem got into 1.3.1.0 update.

Fixes: #283

With the changes introduced in duckdb#276 the `jdbc:duckdb:ducklake:...`
URLs have the special handling: `jdbc_pin_db` and `jdbc_stream_results`
options are applied to them automatically. This behaviour was supposed
to be overridable with URL or `Properties` but by mistake incorrect
method was used for override check. And as DuckLake is still not
available in the `main` branch, there is no test coverage for this and
the problem got into `1.3.1.0` update.

Fixes: duckdb#283
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

cant specify connection property in URL when using ducklake direct attach
1 participant