CatalogueEntry.
The only way to read a file of the lakehouse
Figure 1CatalogueEntryspecified
- kind
- definition
- scope
- follows
- key
- the layer, the plane, the source, the day and the version
- store
- postgres
- family
- record
Fields#
| field | type | required | note |
|---|---|---|---|
layer | one of as landed | refined | ready to use | yes | |
plane | Plane | yes | |
source | Source | no | |
day | date | no | required only when the table is split by day |
files | LakeFile | yes | |
rows | count | yes | |
made_from | [id] | yes | |
table | SilverTable | yes | |
bucket | count | no | for a table split by entity bucket |
snapshot | count | yes | the lakehouse catalogue’s snapshot that is this entry |
version | count | yes | the partition’s version, from the entry’s key |
hash | hash | no | the hash of the partition’s rows, as the closed partition carries it; the commit carries it |
Routes that use it#
No route takes or returns CatalogueEntry directly. The record holds it, and the objects that point at it reach it.