ashb commented on issue #17931: URL: https://github.com/apache/airflow/issues/17931#issuecomment-911530455
> Although it does make writing customised timtable more difficult since now you can only use pre-defined timetable classes instead of inventing things right inside a DAG file. Since the scheduler needs to load the timetable class, and Airflow tries very hard to never load dag code in to a long running process, I think not being able to define it in a DAG file is, sadly, desired behaviour. You'd have to define it in a plugin which can live in `plugins/` along side `dags/`, so users won't have to create a Python dist etc. -- 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]
