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
Process-global manifest cache is keyed only on manifest_path #3978
Its docstring describes it accurately: "Process-wide ManifestFile cache keyed by manifest_path." The key is the path string alone — no catalog, table, session, or tenant forms part of it.
On a hit it returns the cached object and discards the one just read. Since read_manifest_list constructs ManifestFile objects from the entries of a manifest list rather than by reading each manifest file, the cached object reflects whatever the first manifest list to name that path declared — including its partition summaries, counts and sequence numbers.
Two tables in the same process that reference the same manifest_path therefore share one ManifestFile, and the first read wins. Because those fields drive scan pruning, a stale or mismatched entry changes which files a scan considers.
Issue investigation generated via claude, reviewed by Sung, Kevin, Fokko.
I'm not sure if this is a real bug. Sharing manifests between tables is quite controversial, since you don't know who owns the manifest file. If either table expires the manifest, the other table will be bricked.
Activity
fix(manifest): verify cached ManifestFile content before reusing it
Fokko commentedon Sep 17, 2026
I'm not sure if this is a real bug. Sharing manifests between tables is quite controversial, since you don't know who owns the manifest file. If either table expires the manifest, the other table will be bricked.
fix(manifest): scope cache key by table_uuid instead of content compa…
fix(manifest): scope cache key by table_uuid instead of content compa…