ducklink: update to v4.3.0#2214
Merged
Merged
Conversation
Additive minor since v4.2.0. Adds native distribution end-to-end (`.duckdb_extension` builds fetched + cached + sha256-verified through the ducklink catalog, then LOADed by DuckDB), a `DUCKLINK LOAD '<name>' [WASM|NATIVE]` SQL statement (default WASM), a `kind` parameter on the existing `ducklink_load()` table function, and a `native_available` column on `ducklink.modules`. Two DuckDB upstream drafts included in the repo for future ecosystem work (trust-key registration + function-autoload registration). No API breaks; no WIT contract changes.
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Additive minor since v4.2.0. No API breaks, no WIT contract changes.
What's new
Native distribution end-to-end. A new
nativeprovider kind on ducklink catalog entries (platform + duckdb_version + content_digest). Entries with a matching native provider are fetched from ducklink infrastructure, sha256-verified, cached under~/.cache/ducklink/native/…, and LOADed via DuckDB's own extension mechanism. The extension does not flipallow_unsigned_extensions— that's an explicit user choice at DuckDB startup (-unsigned).New SQL surface.
DUCKLINK LOAD '<name>' [WASM|NATIVE];— default WASM. Retires the previousLOAD WASM 'aba'/LOAD NATIVE 'aba'pseudo-LOAD verbs (which borrowed DuckDB's LOAD keyword; the new form is unambiguously ducklink).Function form.
FROM ducklink_load('aba', kind => 'wasm' | 'native')— same choice via the existing table function.Discovery. New
native_availableBOOLEAN column onducklink.modules— TRUE when the entry has a native provider matching this host's platform + DuckDB version.Design docs shipped alongside
Two upstream discussion drafts are in the repo, both ready to file at duckdb/duckdb:
docs/duckdb-upstream-custom-trusted-keys.md— minimal-viable subset of #23388; acustom_trusted_extension_keyssetting so third-party extension distributors can be trusted without globalallow_unsigned_extensions.docs/duckdb-upstream-function-autoload.md— anExtensionHelper::RegisterFunctionEntryAPI so extensions like ducklink can extend DuckDB's function → extension autoload map at runtime. Would enable transparent autoload (SELECT aba_validate(...)with no prior LOAD).Supersedes
#2207 (v4.2.0). Closing that with a supersedes comment.
PR history