Implement `--mark-skipped` on the backfill command
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
Seems loosely related to a few tickets, like #262 which was closed without explanation.
From what I am gathering, following the different links across tickets, everything to do it might have been implemented. Everything but the UI, making it available to end users.
**Use case / motivation**
There exists a `--mark-success` option for the `dags backfill` command but no such `--mark-skipped` option.
Marking a task as success is not equivalent to marking it has skipped, when it comes to later on knowing what happened, e.g. why some data might not have been computed and be missing.
**Are you willing to submit a PR?**
I can try. Maybe some pointers could help.
**Related Issues**
#262 (closed without being implement, applied to the Web UI, not the CLI)
#1155 the ticket suggesting this is possible.
Contributor guide
Research direction
Start by tracing the existing --mark-success option in the dags backfill command and compare its behavior with the expectations described here. Review related issues #262 and #1155 for context; done means a corresponding --mark-skipped option is available and marks the selected tasks as skipped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100