add design assumption on stability of job run read partitions

This commit is contained in:
Stuart Axelbrooke 2025-11-30 23:54:44 +08:00
parent 9c6cb11713
commit 23c3572106

View file

@ -68,4 +68,5 @@ What about situations where data is configured by a web app, etc? Taints are a g
## Assumptions
- Job -> partition relationships are canonical, job runs are idempotent
- The data deps / partitions read by a fully parameterized job run is consistent over time: same parameters = same read partitions