Hi Malthe I really like this feature suggestion, especially since it's crucial for customers who are transitioning from Control-M or Autosys [1] to Airflow. Implementing this feature has the potential to bring Airflow's scheduling capabilities on par with these tools.
> I actually added some sort of forecasting functionality to the calendar view > a while back This is incredible! I was going to bring it up as this becomes essential when scheduling tasks such as "all days except US holidays.". Glad that you already took care of it. > if we had a nicely generated string representation describing the resulting > schedule, perhaps that would be adequate While I understand the importance of having a human-readable string, I agree with Niko that UI configuration is important here. In the same vein as forecasting, having configuration in UI will enable any user to set up these schedules without making any mistakes. Reference: 1. https://www.youtube.com/watch?v=qrwwxDKAY-w&ab_channel=BMCdocs Cheers, Shubham On 2023-03-30, 6:09 AM, "Malthe Borch" <mal...@apache.org <mailto:mal...@apache.org>> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. > I think an interesting topic to discuss for this project would be some kind > of UI based date/calendar picker to help users construct these logical > compositions. Something like `days("D1", "D2", "THU-SAT", "4>", "L1")` is > quite inscrutable. Agreed – and really, the syntax is something to consider further. I think implementing a human-readable `__str__` could perhaps go a long way here! > A UI component to at least visualize the composition you've created would be > super powerful, and if it could be used to modify or create the compositions > that would be an even better user experience. It might be useful, but if we had a nicely generated string representation describing the resulting schedule, perhaps that would be adequate. This could be enough to confirm the developer that they've done it correctly. Anticipating this "rich scheduling" capability, I actually added some sort of forecasting functionality to the calendar view a while back: https://github.com/apache/airflow/pull/22055 <https://github.com/apache/airflow/pull/22055>. Cheers --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org <mailto:dev-unsubscr...@airflow.apache.org> For additional commands, e-mail: dev-h...@airflow.apache.org <mailto:dev-h...@airflow.apache.org> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
