[Filters] Add filtering support to Search - Dags · apache/airflow#53041

2025-07-08T20:17:12.000Z

### 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)

Repository-Metriken

Stars: (44.809 Stars)
PR-Merge-Metriken: (Durchschn. Merge 7T 18h) (834 gemergte PRs in 30 T)

Beschreibung

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

Research-Richtung: Beginnen Sie mit der Untersuchung des aktuellen /dags API Endpunkts in airflow/api connexion/endpoints/dag endpoint.py, um zu verstehen, wie Filter derzeit implementiert sind (z. B. für Status, Tags). Erweitern Sie dann den Endpunkt, um die neuen Filterparameter (has import errors, owners, is stale, timetable, bundle name, bundle version, has asset schedules, schedule interval) zu akzeptieren. Stellen Sie sicher, dass die SQLAlchemy Abfrage in airflow/models/dag.py entsprechend aktualisiert wird. Für das Frontend sehen Sie sich die Search Dags Komponente in airflow/ui/src/views/Search/Dags/ an, um Filter UI Elemente hinzuzufügen, die mit den vorhandenen Filtern konsistent sind. Die Issue Kommentare können weitere Anleitungen zur erwarteten Implementierung liefern.
Tech Stack: pythonjavascripttypescript
Domain: backendfrontend
Issue Type: Funktion
Schwierigkeit: 3
Geschätzte Zeit: 1-2 Tage
Aktivitätsstatus: Aktiv
Klarheit: Meist klar
Voraussetzungen: PythonREST APIReact
Einsteigerfreundlichkeit: 60