GC cases
Test cases for deleting shared objects, which every implementation runs and agrees on.
cases/gc.json holds datasets and, for each, the shared objects a process that deletes them (Data files) deletes. An implementation that deletes shared objects runs every case and deletes exactly those. Stopping with an error counts as deleting nothing, so it meets a case only when that case deletes nothing.
{
"now": "2026-11-12T00:00:00Z",
"grace_seconds": 86400,
"cases": [
{
"name": "keeps the data files a live version's tables.json lists",
"files": { "fdl.json": {}, "versions/<ID>/version.json": {}, "versions/<ID>/tables.json": {} },
"objects": { "tables/main/t/ducklake-a.parquet": "2026-11-01T00:00:00Z" },
"deleted": ["tables/main/t/ducklake-c.parquet"]
}
]
}
| Key | Holds |
|---|---|
now, grace_seconds |
The time the process runs, and the grace period |
files |
The dataset’s files other than shared objects, by key. Each value is the file’s JSON |
objects |
The objects under the data directory and assets/, and files elsewhere a process must leave alone, by key, with the time each was placed. Their content does not matter |
metadata |
The tables of a metadata file, by the metadata’s key: each table’s column types and rows. A case holds only the tables it needs, such as those with asset columns |
deleted |
The keys deleted |
A change to what may be deleted comes with a case here, in the same change as this specification.