The old last_partition default here doesn't work very well wtih the new scheduler, which might be doing catchup and filling in multiple partitions. The schedule decorators pass in a smarter default in here - make th
at default more discoverable for users, and require a user who wants to create a schedule from a partition set to be more explicit about how each execution should match to a partition (by using that default function, or some other partition selector that they write).
Details
Details
BK
Diff Detail
Diff Detail
- Repository
- R1 dagster
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Comment Actions
OK, I ended up changing this a bit since leaving people with no suggested function to use felt weird. I basically made the partition selectors that the built-in decorators use public (and a bit more user-friendly) and added comments / examples / put them in the apidocs. Would you mind taking another look?
| python_modules/dagster/dagster/utils/partitions.py | ||
|---|---|---|
| 188 | sure, I can add this (as well as date_partition_range? that wasn't in there either) | |
