rawwar commented on issue #53043: URL: https://github.com/apache/airflow/issues/53043#issuecomment-3217135050
I'm not sure if we should support Duration range. We don't have this data readily available and DagRun needs to be computed on the go. Also, our search filters are currently triggered by change in the field. If someone wants to type "523" seconds. I am not sure if its going to hit queries for 5 and then 52 and then 523 by the time user completes typing into the search box. And, that I think is going to be compute intensive on DB. Maybe not too much when user is already on a Dag Page. As we do filter by Dag Id. But, if on the page Dags-> DagRuns, its going to run this on all of the data in DagRun table. If my concern sounds legit, we can update DagRun Model to have duration column(its currently a hybrid property). Then have duration_<lte|lt|gte|gt> params -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
