amoghrajesh commented on PR #67118: URL: https://github.com/apache/airflow/pull/67118#issuecomment-4518682039
@jscheffl thanks for your review. I agree that deferrable should remain the recommended path for long-running tasks — that is not what this is trying to change. The goal here is much narrower: making the existing sync path "survivable" for teams already on it. The framing I would probably use here is: `ResumableJobMixin` is not "a better alternative to Triggerer" — it is more of a safety net for the _sync path_ that already exists. If you are running sync operators today (and many teams are, for log observability, complexity, or org constraints), you get crash recovery. If you want to move to deferrable, nothing here blocks that, the two paths are independent. And tbh, it's not a question of sync vs async, but making sync better for teams who can't or won't do async right now. I will make this explicit in the mixin's docstring so it's clear to anyone reading the code. -- 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]
