-
Notifications
You must be signed in to change notification settings - Fork 16.4k
[AIRFLOW-6867] Decouple DagBag and TaskInstance #7488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| CYCLE_DONE = 2 | ||
| DAGBAG_IMPORT_TIMEOUT = conf.getint('core', 'DAGBAG_IMPORT_TIMEOUT') | ||
| UNIT_TEST_MODE = conf.getboolean('core', 'UNIT_TEST_MODE') | ||
| SCHEDULER_ZOMBIE_TASK_THRESHOLD = conf.getint('scheduler', 'scheduler_zombie_task_threshold') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still needed in here? Feels like it shouldn't be
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know. I just do simple refactoring. I don't know the history of this option.
Codecov Report
@@ Coverage Diff @@
## master #7488 +/- ##
==========================================
- Coverage 86.68% 86.46% -0.23%
==========================================
Files 882 883 +1
Lines 41526 41634 +108
==========================================
+ Hits 35997 35998 +1
- Misses 5529 5636 +107
Continue to review full report at Codecov.
|
|
@mik-laj there is typo Simpley |
|
@tooptoop4 Thanks. I will try to correct all types in the schedule when I finish optimizing the scheduler. |
The refactor in apache#7488 introduced a scheduler-breaking bug.
DagBag should be responsible for loading DAGs. The Scheduler should be responsible for managing task instance.
Issue link: AIRFLOW-6867
Make sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX].In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.