[
https://issues.apache.org/jira/browse/AIRFLOW-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bas Harenslak updated AIRFLOW-4039:
-----------------------------------
Description:
I think the /blocked endpoint could be improved in various ways:
* Give more meaningful name. It returns a list of DAG ids and corresponding
active dag runs & max dag runs. Could be named e.g. "max_dagruns".
* The tooltip doesn't work for (running on Chrome 72). tooltip() is called in
dags.html, but I only see the attribute when hovering over the schedule of a
DAG.
* The info is fetched and returned for all DAG runs, while there is pagination
in the Airflow UI. Would make sense to fetch only the dagrun counts for the DAG
ids on the shown page.
* We should persist max_active_runs in the database to avoid re-parsing DAG
files.
was:
I think the /blocked endpoint could be improved in various ways:
* Give more meaningful name. It returns a list of DAG ids and corresponding
active dag runs & max dag runs. Could be named e.g. "max_dagruns".
* The tooltip doesn't work for (running on Chrome 72). tooltip() is called in
dags.html, but I only see the attribute when hovering over the schedule of a
DAG.
* The info is fetched and returned for all DAG runs, while there is pagination
in the Airflow UI. Would make sense to fetch only the dagrun counts for the DAG
ids on the shown page.
> Fix various issues on the /blocked endpoint
> -------------------------------------------
>
> Key: AIRFLOW-4039
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4039
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Bas Harenslak
> Priority: Major
>
> I think the /blocked endpoint could be improved in various ways:
> * Give more meaningful name. It returns a list of DAG ids and corresponding
> active dag runs & max dag runs. Could be named e.g. "max_dagruns".
> * The tooltip doesn't work for (running on Chrome 72). tooltip() is called
> in dags.html, but I only see the attribute when hovering over the schedule of
> a DAG.
> * The info is fetched and returned for all DAG runs, while there is
> pagination in the Airflow UI. Would make sense to fetch only the dagrun
> counts for the DAG ids on the shown page.
> * We should persist max_active_runs in the database to avoid re-parsing DAG
> files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
