[Filters] Add filters to Asset View
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### View
Asset View
### Filters to Add
- Filter by **Event Timestamp (Range)**
↪ Focus on recent or historical asset events within a specific window
- Filter by **DAG ID**
↪ Isolate events triggered by a specific DAG
- Filter by **Task ID**
↪ Track asset events back to the producing task
- Filter by **Event Type** (e.g., manual, scheduler-created, via asset watcher)
↪ Differentiate programmatic updates from ad-hoc, scheduler created or asset events created via asset watchers
### API Support
⚠️ Partial
- The `asset_events` API includes all fields, but filtering is not fully implemented or exposed in the UI
- Some filters (e.g., timestamp range) may need to be implemented on the backend or via query parameters
### UI Impact
- Add a filter bar or collapsible panel above the event list
- Improves readability and analysis of high-volume asset event streams
### Notes
- Especially useful in asset-triggered DAGs and debugging incorrect lineage or asset duplication
Contributor guide
Research direction
Start by reviewing the Asset View event list and the asset_events API to determine which fields and query parameters already support filtering. Done means the UI exposes event timestamp range, DAG ID, task ID, and event type filters, with backend support where needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, data-engineering, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100