Hi,

My name is Alvaro and I am a junior developer who is writing his FMP (Final
master project) about a project which uses Apache Airflow. I am interested
in developing a new feature for Airflow which I think many people could use.

MOTIVATION
I really think this is a very useful feature to add. There are times when
you want to make a dag execution and you expect that execution to overtake
the others already running, because it has priority over them. Now, this is
not possible, because the tasks priority are static and only added when
creating a dag, not when doing a dag run.

CONSIDERATIONS
I propose to add a parameter to the dag run API and Client endpoint named
as 'priority'. This parameter will overwrite the tasks priority of the new
dag run. Then, the scheduler will do the work as it does now.
This will remove the need of creating several dags which do the same but
with different priority parameters.
Users are not affected by this change, because it is a change that adds an
optional parameter that can be used or not.

I will extend the AIP proposal when I get access to the Confluence AIP
Draft.

Thanks in advance.

Reply via email to