[Filters] Add filters to DAG View - Backfills Tab · apache/airflow#53049

2025-07-08T21:46:27.000Z

### View **DAG View – Backfills Tab** ### Filters to Add - Filter by **Start Date / End Date** ↪ Useful to isolate backfills that targeted a specific data range - Filter by **Created At** ↪ Helps identify when backfills were initiated (e.g., ad hoc vs. automated) - Filter by **Completed At** ↪ Enables monitoring of completion lag or stuck backfills - Filter by **Duration** ↪ Surfaces long-running backfills that may impact system performance - Filter by **Reprocess Behavior** ↪ Distinguish between missing-only backfills and full-range reprocessing - Filter by **Max Active Runs** ↪ Useful when diagnosing throttling or concurrency constraints in backfill execution - Filter by **Status** ↪ Surface failed or incomplete backfills ### API Support ✅ Yes - `/dags/{dag_id}/backfills` supports filtering via: - `start_date`, `end_date` - `created_at`, `completed_at` - `status`, `table.duration`, `table.reprocessBehavior`, `max_active_runs` ### UI Impact - Add filter controls above the backfill table (consistent with DAG Runs tab) - Consider sortable columns and pill filters for behavior or status - Could also support "re-run" or "cancel" from filtered selection ### Notes - Users often need to investigate reprocessing activity during incidents - Filtering helps correlate performance issues with large or frequent backfills

(4 留言) (0 反應) (1 負責人)Python (44,809 star) (16,781 fork)batch import

area:UIgood first issuekind:featurekind:meta

描述

View

DAG View – Backfills Tab

Filters to Add

Filter by Start Date / End Date
↪ Useful to isolate backfills that targeted a specific data range
Filter by Created At
↪ Helps identify when backfills were initiated (e.g., ad hoc vs. automated)
Filter by Completed At
↪ Enables monitoring of completion lag or stuck backfills
Filter by Duration
↪ Surfaces long-running backfills that may impact system performance
Filter by Reprocess Behavior
↪ Distinguish between missing-only backfills and full-range reprocessing
Filter by Max Active Runs
↪ Useful when diagnosing throttling or concurrency constraints in backfill execution
Filter by Status
↪ Surface failed or incomplete backfills

API Support

✅ Yes

/dags/{dag_id}/backfills supports filtering via:
- start_date, end_date
- created_at, completed_at
- status, table.duration, table.reprocessBehavior, max_active_runs

UI Impact

Add filter controls above the backfill table (consistent with DAG Runs tab)
Consider sortable columns and pill filters for behavior or status
Could also support "re-run" or "cancel" from filtered selection

Notes

Users often need to investigate reprocessing activity during incidents
Filtering helps correlate performance issues with large or frequent backfills

貢獻者指南

技術棧: pythonreacttypescript
領域: frontendbackend
議題類型: feature
難度: 3
預計時間: 1-2 days
活動狀態: active
清晰度: clear
前置要求: PythonReactREST API basics
新手友善度: 65
研究方向: The issue requests adding filter controls to the Backfills tab in the DAG View. API support already exists via the `/dags/{dag id}/backfills` endpoint with query parameters like `start date`, `end date`, `status`, etc. The UI should be consistent with the existing DAG Runs tab filters. Look at the current Backfills tab implementation in the Airflow UI source code (likely under `airflow/ui/src/views/Dag/Backfills`). The filters should be added as pill filters or dropdowns above the table. Consider reusing filter components from the DAG Runs tab. For the duration and max active runs filters, you may need to use range inputs. No linked PRs or blockers mentioned.