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

Métriques du dépôt

Stars: (44 809 stars)
Métriques de merge PR: (Merge moyen 7j 18h) (834 PRs mergées en 30 j)

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)

Guide contributeur

Direction de recherche: Commencez par examiner le point de terminaison API /dags actuel dans airflow/api connexion/endpoints/dag endpoint.py pour comprendre comment les filtres sont actuellement implémentés (par exemple pour le statut, les tags). Étendez ensuite le point de terminaison pour accepter les nouveaux paramètres de filtre (has import errors, owners, is stale, timetable, bundle name, bundle version, has asset schedules, schedule interval). Assurez vous de mettre à jour la requête SQLAlchemy dans airflow/models/dag.py en conséquence. Pour le frontend, regardez le composant Search Dags dans airflow/ui/src/views/Search/Dags/ pour ajouter des éléments d'interface utilisateur de filtre cohérents avec les filtres existants. Les commentaires de l'issue peuvent fournir des conseils supplémentaires sur l'implémentation attendue.
Stack technique: pythonjavascripttypescript
Domaine: backendfrontend
Type d'issue: Fonctionnalité
Difficulté: 3
Temps estimé: 1-2 jours
Statut d'activité: Active
Clarté: Plutôt claire
Prérequis: PythonREST APIReact
Accessibilité débutant: 60