uranusjr commented on issue #51549: URL: https://github.com/apache/airflow/issues/51549#issuecomment-3226822679
Most of the timetable logic need to be in the scheduler. So we should kind of do the opposite of SerializedBaseOperator. 1. Existing tiemtable classes in core are scheduler-only. 2. Create timetable “stub” classes that only takes arguments without any scheduler logic. 3. The stubs are serialised, and deserialised in the scheduler into their “real” timetable class counterparts. Custom subclasses are more problematic. I guess for now (Airflow 3.1) we can just make that one single subclass fulfill both roles as a stub and real timetable. Maybe at some point we need to have an Airflow Extension SDK for this, and other things plugin-wise that you can register into the scheduler. -- 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]
