You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use WAL mode for the REST fixture's SQLite backend #18043
apache/iceberg-rest-fixture runs JdbcCatalog on a file-backed SQLite db using sqlite's default rollback journal. That mode only lets one connection touch the db at a time, so when several clients hit the fixture in parallel, which is what every integration suite does, one of them eventually fails with SQLITE_BUSY ("database is locked").
WAL mode lets reads and the write happen side by side, so there's nothing to fight over. It's a one-line change to the JDBC URI and it should be the default. Details, stress numbers, and the reasoning against the alternatives (busy_timeout, retries, serializing tests) are in apache/iceberg-rust#3183.
Several repos also set CATALOG_URI=jdbc:sqlite:file:/tmp/iceberg_rest_mode=memory, inherited from the old databricks/iceberg-rest-image, which hard-coded it as its default. iceberg_rest_mode isn't an option, there's no ? in the URI so it's just part of the filename. Those overrides should be replaced with the same WAL URI rather than carried along.
Repos that don't set CATALOG_URI (iceberg-python, the iceberg-go recipe, terraform-provider-iceberg, the Flink quickstart) need nothing: they pick up WAL automatically once they bump to an image with the new default, or can set the env var themselves in the meantime.
Apache projects still on the old tabulario/iceberg-rest image (druid, texera, a doris sample) have the same backend and would need to move to apache/iceberg-rest-fixture first. Out of scope here, listed for completeness.
Activity
kevinjqliu commentedon Sep 10, 2026
all done!