transactions, balances, ledgers, and identity.
They connect on shared IDs, so a transaction can be read with the balance it touched, the ledger that balance belongs to, and the identity that owns it.
Confirm column names and types with Get lake schema.
How they connect
Balances sit in the middle. Each balance belongs to one ledger and can belong to one identity. Each transaction points at two balances: source is where money leaves, and destination is where money arrives. A transaction row stores balance IDs, not names. The identity name lives onidentity, and the ledger name lives on ledgers. Follow destination or source to the balance, then to the identity or the ledger.
A balance, ledger, or identity keeps one ID for its lifetime. The lake can store more than one copy of that ID across days. See Data Lake.
A lake transaction row has one source and one destination. For transactions that split across many balances, see Multiple sources and Multiple destinations.
Tables and columns
- transactions
- balances
- ledgers
- identity