potiuk commented on PR #30083: URL: https://github.com/apache/airflow/pull/30083#issuecomment-1473376843
> > But maybe a flag on the existing cron timetable is acceptable? Something obvious like `adjust_for_dst` and possibly even a warning if you have a schedule that will be affected and don't set this flag. > > The thing here is the semantic of `schedule="<cron expr>"` (or `schedule_interval`, they are the same) _cannot_ change (until Airflow 3.0) due to compatibility policies. And you can’t dismiss the current behaviour as a bug; the fact it is ensured by test means the behaviour is delibrately designed by someone, and likely relied on someone as a feature. Yeah. agree it's something we should be careful about, but having "adjust_standard_cron_for_dst" flag in the DAG and raising deprecation warning in case if someone uses "regular" cron and has this flag "false" sounds completely doable and way better for potential breaking change in case we have Airflow 3 than having a separate timetable IMHO. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
