We thenĬreate a DataInterval object to describe this The start of the interval, the end is simply one full day after it. Sunday), it should be pushed further back to the previous Friday. Run_after falls on a Sunday or Monday (i.e. Should usually start at the midnight one day prior to run_after, but if Since our timetable createsĪ data interval for each complete work day, the data interval inferred here That indicates when the DAG is externally triggered. The method accepts one argument run_after, a pendulum.DateTime object get_next_workday ( start, incr =- 1 ) return DataInterval ( start = start, end = ( start + timedelta ( days = 1 ))) replace ( tzinfo = UTC ) # Skip backwards over weekends and holidays to find last run start = self. combine (( run_after - timedelta ( days = 1 )). No runs happen on midnights Sunday and Monday.ĭo not schedule a run on defined holidays.įor simplicity, we will only deal with UTC datetimes in this example.ĭef infer_manual_data_interval ( self, run_after : DateTime ) -> DataInterval : start = DateTime. Monday happens on midnight Tuesday and so on. Run’s data interval would cover from midnight of each day, to midnight of theĮach run would be created right after the data interval ends. Schedule a run for each Monday, Tuesday, Wednesday, Thursday, and Friday. Further, the above schedule string cannot skip This means data collected on Friday will not be processed right after FridayĮnds, but on the next Monday, and that run’s interval would be from midnightįriday to midnight Monday. Would be schedule="0 0 * * 1-5" (midnight on Monday to Friday), but Process data collected during the work day.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |