frosk1 edited a comment on issue #10194: URL: https://github.com/apache/airflow/issues/10194#issuecomment-690916489
@Shadowsong27 it is nice to see more reminiscence and feedback on this topic. I have been gone the complete way from a outside enduser view to force airflow becoming more flexible in its scheduling mechanism: opened feature request[ #10449](https://github.com/apache/airflow/issues/10449), send draft via mail to [email protected], etc. Within my feature request I point out the huge huge demand coming from endusers in terms of stackoverflow discussions, where users not even see this being under development. Having said this, airflow should integrate full stack scheduling behavior to fill the gap. It is not a huge feature request to realize this and also airflow could step up to cover all former cron based systems and make them obsolete. To have not only a really really great worflow handling software but also the state of the art scheduling software. I think I did everything I could to point the airflow community on to that topic, which is based by a huge enduser demand. At my own firm we are applying airflow and we would also loved to see this step up. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
