apache/airflow

[Filters] Add filtering support to Search - Dags

Open

#53,041 opened on Jul 8, 2025

View on GitHub
 (20 comments) (2 reactions) (1 assignee)Python (44,809 stars) (16,781 forks)batch import
area:UIgood first issuekind:feature

Description

View

Search - Dags

Filters to Add

  • Filter DAGs with Import Errors ↪ has_import_errors = true

  • Filter DAGs by Owner ↪ owners = ['alice', 'bob', 'airflow']

  • Filter Stale DAGs ↪ is_stale = true

  • Filter DAGs by Timetable ↪ (e.g. CronTriggerTimetable, AssetOrTimeSchedule)

  • Filter DAGs by Bundle Name or Version ↪ bundle_name = 'analytics', bundle_version = 'v1.2.3'

  • Filter DAGs with Asset-Based Schedules ↪ Requires awareness of upstream asset dependencies

  • Filter Unscheduled DAGs ↪ schedule_interval = None or equivalent

API Support

⚠️ Partial

  • /dags returns many required fields (has_import_errors, is_stale, bundle_name, owners)
  • But does not currently support these as filter query parameters
  • Would require extending the DAG API to support additional filters

UI Impact

  • Filters would appear at the top of the Search – DAGs screen
  • Should be consistent with filters for status, tags, and active/paused state already present
  • Multi-select or autocomplete where applicable (e.g., owners)

Contributor guide

Tech stack
pythonreact
Domain
full stack
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
PythonJavaScript/ReactAirflow DAG concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Start by examining the current /dags API endpoint in airflow/api connexion/endpoints/dag endpoint.py to understand how filters are currently implemented (e.g., for status, tags). Then extend the endpoint to accept the new filter parameters (has import errors, owners, is stale, timetable, bundle name, bundle version, has asset schedules, schedule interval). Ensure the SQLAlchemy query in airflow/models/dag.py is updated accordingly. For the frontend, look at the Search Dags component in airflow/ui/src/views/Search/Dags/ to add filter UI elements consistent with existing filters. The issue comments may provide further guidance on the expected implementation.