Investigate whether to move LoginMixin to task sdk
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Body
Reference: https://github.com/apache/airflow/pull/51873#discussion_r2162980979
> I just realised BaseOperator does not depend on LoggingMixin anymore. (DAGNode now implements its own log property.) This should probably do the same. Maybe we should have a LoggingMixin in the sdk that just implements this.
### Committer
- [x] I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Contributor guide
Research direction
Start with the discussion in apache/airflow#51873 and compare the current LoginMixin or LoggingMixin usage with BaseOperator and DAGNode. Determine whether the mixin should move into the task SDK, then document the affected dependencies and the intended SDK ownership as the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100