v4.4.0

chdb 4.4.0

Requires chdb-core>=26.7.0; the durable extras require chdb-core>=26.7.3.

New

chdb.durable (#634, #635, #640) — a chDB database whose state lives in object storage you own. Restore is fast, a lease makes single-writer a guarantee, and an object is a folder you can move between clouds. Objects it writes are readable by the Node and Go bindings, and vice versa.

from chdb import durable as cd
ns = cd.Namespace("s3://bucket/prefix", owner="worker-1")
obj = ns.open("user-123")                        # lease + restore
obj.execute("INSERT INTO beliefs VALUES (...)")  # local; buffered
obj.flush()                                      # now it survives losing this machine
obj.checkpoint()                                 # fold into a fresh base
obj.close()

pip install "chdb[durable]" for S3-compatible storage (AWS, MinIO, R2, GCS via its S3 endpoint), or chdb[durable-gcs] / chdb[durable-azure] for the native ones. See docs/durable.

Breaking, if you used the durable preview in 4.3.0

That was a prototype; this is the frozen V1 protocol and replaces it.

• Objects written by the prototype cannot be opened — their checkpoints carry no checksum, so they cannot be verified. Re-create the object.
• A new object is created in default, not mem. Existing objects keep the name in their head.
• A namespace URL may be local: or file:// — one URL now fits Python, Node and Go.

Full Changelog: v4.3.0...v4.4.0