Expand description
All of the protobuf types we durably persist in the Catalog.
These exist outside of the mz_catalog
crate because the code generated by
prost
for the protobuf files, takes a considerable (>40s) amount of
time to build
and even check
, yet the protobuf files rarely change. So
moving them into a separate crate allows folks to iterate on the
mz_catalog
crate without having to pay the cost of re-compiling these
protobuf files.
Modules§
- audit_
log - This module is responsible for serializing objects from the
mz_audit_log
crate into protobuf. - objects
- objects_
v67 - objects_
v68 - objects_
v69 - objects_
v70 - objects_
v71 - objects_
v72 - objects_
v73 - objects_
v74 - serialization
- This module is responsible for serializing objects from crates other than
mz_catalog
into protobuf.
Macros§
Constants§
- CATALOG_
VERSION - The current version of the
Catalog
. - MIN_
CATALOG_ VERSION - The minimum
Catalog
version number that we support migrating from.