InferredSchema
The model the catalog derives from the store's segments.
This is the answer to "what is actually in there", and it is produced by folding the per-segment sketches rather than by scanning — so asking for it costs the fold, not the data.
Two approximations are inherent and are not bugs. A key that has been overwritten but not yet compacted is counted once per segment that holds a live version, and a deleted document's earlier contribution survives until compaction drops the superseded version. Both have the same cause — an LSM tree holds several versions of a key until it merges them — and the same fix, which is DocumentStore.compact(). Against an append-only or compacted store the counts are exact.
Properties
How much of the store contributed. See CatalogCoverage.
Documents the model accounts for. See the class documentation for what "accounts for" means.
Every tracked path, in canonical order.
Whether any path was dropped for exceeding the budget.
Observations that belonged to a dropped path.
Estimated distinct paths dropped for exceeding CatalogOptions.maxPaths.
Functions
The field at path, or null if the catalog does not track it.
The field at the path expression parses to. See CatalogPath.parse.