Skip to content

v3.4.0

chdb-node v3.4.0 — durable on a stable engine
@ShawnChen-Sirius ShawnChen-Sirius tagged this 17 Sep 05:07 
The first release where `chdb/durable` works out of the box. The addon binds
the Durable V1 ABI (`chdb_version`, `chdb_backup_database_n`,
`chdb_restore_database_n`, `chdb_classify_query_n`) and `chdb/durable/node`
ships the default engine over it, so a Node caller supplies an engine factory
rather than a symbol table:

    import { DurableNamespace, nodeEngineFactory } from 'chdb/durable/node'

Engine `26.7.3`, the first stable release carrying that ABI.

New in this release:

- `chdb/durable/node` — the default `EngineAdapter` over the addon. Importing
  it loads no native code; the addon arrives when `open()` first builds an
  engine, which is also where the ABI is checked.
- `SessionOptions.connectionArgs` — engine arguments that cannot be a `SET`,
  such as `--async_load_databases=0` and `--config-file=…`.
- The local durable backend answers to `local:` as well as `file:`, matching
  Python and Go, so one namespace URL works across bindings.
- `@aws-sdk/client-s3` is loaded on first use, so `chdb/durable/s3` imports
  without it and says what to install when it is needed.

Verified on `26.7.3`: 141 protocol/state-machine cases, 24 over the addon, 486
in the v3 suite, 19 end-to-end under Bun, 11/11 S3 provider conformance and
4/4 full stack against both MinIO and real AWS S3, a newer engine restoring an
older engine's archive, and cross-binding exchanges with Python `chdb` 4.4.0
and `chdb-go` in both directions.

Cloudflare R2 is untested. `chdb/durable` remains experimental.
Assets 2
Loading