Rename task_concurrency to max_active_tis_per_dag#17708
Conversation
adb98e2 to
ce5f881
Compare
There was a problem hiding this comment.
What's the purpose of this test BTW? We had another PR About it and I was not sure why we have the list here.
There was a problem hiding this comment.
This list just makes sure that if new fields are added to the base operator we add it here, in case it needs any special treatment for DAG Serialization (helpful if they are dicts and lists)
|
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
ce5f881 to
4f1d55c
Compare
Follow-up of apache#16267 Renames `task_concurrency` to `max_active_tis_per_dag` Some of Airflow's concurrency settings have been a source of confusion for a lot of users (including me), for example: https://stackoverflow.com/questions/56370720/how-to-control-the-parallelism-or-concurrency-of-an-airflow-installation https://stackoverflow.com/questions/38200666/airflow-parallelism This PR is an attempt to make the settings easier to understand
4f1d55c to
5176677
Compare
Follow-up of #16267
Renames
task_concurrencytomax_active_tis_per_dagSome of Airflow's concurrency settings have been a source of confusion for a lot of users (including me), for example:
This PR is an attempt to make the settings easier to understand
ToDo:
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.