Paths/Data Engineer/Batch Ingestion & ETL / Transforms & Contracts
Write a Data Contract
The producer owns the shape of the data. Publish the contract, state how breaking changes are handled, and nobody is surprised on a Monday morning.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/pipelines/contracts/orders.yaml exists○
- The contract states the version and the schema○
- The contract states the compatibility mode○
- The contract states how a breaking change is announced○
02Walkthrough
1 of 4 revealed- 01
Write the contract header
The version is the contract. Consumers pin it, so a change means a new version rather than a surprise.
echo 'contract: orders\nversion: 3\nowner: orders-team\ncompatibility: backward' > ~/pipelines/contracts/orders.yaml - 3 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list