add design assumption on stability of job run read partitions
This commit is contained in:
parent
9c6cb11713
commit
23c3572106
1 changed files with 1 additions and 0 deletions
|
|
@ -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
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue