Skip to content

Conversation

staticlibs
Copy link
Collaborator

This is a manual backport of the PR #258 to v1.3-ossivalis stable branch.

The support for direct attach, was recently added to DuckLake in duckdb/ducklake#201. JDBC connection string example:

jdbc:duckdb:ducklake:postgres:postgresql://user:[email protected]:5432/lake1

This change enables jdbc_stream_results and jdbc_pin_db options by default (unless they are specified by user) for DuckLake connections.

Testing: test coverage pending as DuckLake is not yet available in the main barnch.

This is a manual backport of the PR duckdb#258 to `v1.3-ossivalis` stable
branch.

The support for direct attach, was recently added to DuckLake in
duckdb/ducklake#201. JDBC connection string example:

```
jdbc:duckdb:ducklake:postgres:postgresql://user:[email protected]:5432/lake1
```

This change enables `jdbc_stream_results` and `jdbc_pin_db` options
by default (unless they are specified by user) for DuckLake connections.

Testing: test coverage pending as DuckLake is not yet available in the
`main` barnch.
@staticlibs staticlibs merged commit 258866f into duckdb:v1.3-ossivalis Jun 16, 2025
10 checks passed
@staticlibs staticlibs deleted the ducklake_defaults_13 branch June 16, 2025 11:22
staticlibs added a commit to staticlibs/duckdb-java that referenced this pull request Jun 20, 2025
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
staticlibs added a commit to staticlibs/duckdb-java that referenced this pull request Jun 24, 2025
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
staticlibs added a commit that referenced this pull request Jul 8, 2025
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
staticlibs added a commit to staticlibs/duckdb-java that referenced this pull request Jul 8, 2025
This is a backport of the PR duckdb#287 to `v1.3-ossivalis` stable branch.

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
staticlibs added a commit that referenced this pull request Jul 8, 2025
This is a backport of the PR #287 to `v1.3-ossivalis` stable branch.

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
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.

1 participant