Skip to content
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

Remove dag processor from the scheduler #45729

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

jedcunningham
Copy link
Member

We will only support a standalone DAG processor. Doing so removes complexity from the scheduler, and offers better isolation between these two different workloads.

We will only support a standalone DAG processor. Doing so removes
complexity from the scheduler, and offers better isolation between these
two different workloads.
@jedcunningham jedcunningham added the full tests needed We need to run full set of tests for this PR to merge label Jan 17, 2025
@boring-cyborg boring-cyborg bot added area:API Airflow's REST/HTTP API area:CLI area:Scheduler including HA (high availability) scheduler area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues kind:documentation labels Jan 17, 2025
@jedcunningham jedcunningham added legacy ui Whether legacy UI change should be allowed in PR legacy api Whether legacy API changes should be allowed in PR labels Jan 17, 2025
@jedcunningham jedcunningham reopened this Jan 17, 2025
@kaxil
Copy link
Member

kaxil commented Jan 17, 2025

Nice, look at all that deleted code 👨‍💻!!!

@kaxil
Copy link
Member

kaxil commented Jan 17, 2025

#protm

@potiuk
Copy link
Member

potiuk commented Jan 17, 2025

We'll have many good candidates this month

Copy link
Contributor

@jscheffl jscheffl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool.

This will be a hard choice for PR of the month in Jan 2025...

@jscheffl
Copy link
Contributor

Can you please add a newsfragment before merging because from deployment point of view it is a breaking change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:API Airflow's REST/HTTP API area:CLI area:Scheduler including HA (high availability) scheduler area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues full tests needed We need to run full set of tests for this PR to merge kind:documentation legacy api Whether legacy API changes should be allowed in PR legacy ui Whether legacy UI change should be allowed in PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants