Skip to main content

Module catalog_manifest

Module catalog_manifest 

Source
Expand description

Cluster-wide catalog manifest: the ordered DDL needed to rebuild a node’s logical catalog (sources, tables, streams, materialized views, sinks).

Unlike AssignmentSnapshot (one immutable object per version, CAS-rotated), the catalog manifest is a single mutable object at catalog/manifest.json that the cluster overwrites as DDL changes. A node joining or restarting reads it and replays any DDL it lacks locally so its operator graph exists before the pipeline starts — the data sharded across vnodes then flows into the rebuilt views.

Entries are stored in creation order so a dependent view (one selecting from another) is replayed after its dependency.

Structs§

CatalogManifest
The full ordered set of DDL defining a cluster’s catalog.
CatalogManifestEntry
One catalog object’s defining DDL.
CatalogManifestStore
I/O wrapper for the CatalogManifest on an object store.

Enums§

CatalogManifestError
Errors loading or saving a CatalogManifest.