[
https://issues.apache.org/jira/browse/AIRFLOW-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522532#comment-16522532
]
Ash Berlin-Taylor edited comment on AIRFLOW-1853 at 6/25/18 5:01 PM:
---------------------------------------------------------------------
The new query has {{.limit(num_runs)}} in it -- does that not achieve the
desired effect too, but at the database level?
was (Author: ashb):
The new query has {{ .limit(num_runs) }} in it -- does that not achieve the
desired effect too, but at the database level?
> 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
> Assignee: Matthew Bowden
> Priority: Major
> Fix For: 2.0.0
>
>
> 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)
