You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Matthew Bowden (JIRA)" <ji...@apache.org> on 2018/05/01 17:04:00 UTC
[jira] [Commented] (AIRFLOW-1853) tree view of manually triggered
dags overpopulate page
[ https://issues.apache.org/jira/browse/AIRFLOW-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459863#comment-16459863 ]
Matthew Bowden commented on AIRFLOW-1853:
-----------------------------------------
FWIW this is still an issue - we've encountered this with our own manually triggered dags.
> tree view of manually triggered dags overpopulate page
> ------------------------------------------------------
>
> Key: AIRFLOW-1853
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1853
> Project: Apache Airflow
> Issue Type: Bug
> Components: webapp
> Affects Versions: 1.8.2
> Environment: running from https://github.com/puckel/docker-airflow
> Reporter: Yee Ting Li
> Priority: Major
>
> i have a DAG that i only ever run via an external trigger (via TriggerDagRunOperator). They show up fine under the Tree View, however, the page appears to ignore a filter for the last 25/50... number of runs. Instead, the entire history of all the run's show up on the page - ie if i had triggered the DAG 5 times, it will show all 5... if i have triggered it 500 times it will show all 500 dag runs.
> this also means that loading the page is very very slow with a large number of (triggered) dag runs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)