-
Notifications
You must be signed in to change notification settings - Fork 16.4k
AIP-72: Remove DAG pickling #43667
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
Merged
Merged
AIP-72: Remove DAG pickling #43667
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jedcunningham
previously approved these changes
Nov 4, 2024
Oh, actually, going to wait until KE & CE are done :) But so far looks good!
Member
Author
|
@jedcunningham Done now :) - c6505d7 |
jedcunningham
approved these changes
Nov 4, 2024
f998628 to
4464668
Compare
This was a less used part of Airflow and does not make sense to keep it since we are removing DB access as part of AIP-72, I am removing it here. This was missed in Airflow 2.0!
4464668 to
a4068c0
Compare
topherinternational
pushed a commit
to topherinternational/airflow
that referenced
this pull request
Nov 5, 2024
This was a less used part of Airflow and does not make sense to keep it since we are removing DB access as part of AIP-72, I am removing it here. This was missed in Airflow 2.0! * Handle executors in the providers for Airflow <3 support
kaxil
added a commit
to astronomer/airflow
that referenced
this pull request
Nov 12, 2024
Follow-up of apache#43667
kaxil
added a commit
to astronomer/airflow
that referenced
this pull request
Nov 12, 2024
Follow-up of apache#43667
kaxil
added a commit
to astronomer/airflow
that referenced
this pull request
Nov 12, 2024
Follow-up of apache#43667
kaxil
added a commit
to astronomer/airflow
that referenced
this pull request
Nov 12, 2024
Follow-up of apache#43667
ellisms
pushed a commit
to ellisms/airflow
that referenced
this pull request
Nov 13, 2024
This was a less used part of Airflow and does not make sense to keep it since we are removing DB access as part of AIP-72, I am removing it here. This was missed in Airflow 2.0! * Handle executors in the providers for Airflow <3 support
ellisms
pushed a commit
to ellisms/airflow
that referenced
this pull request
Nov 13, 2024
1 task
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this pull request
May 27, 2025
Follow-up of apache/airflow#43667 GitOrigin-RevId: 5241132a914b4cd4879f6b44ac28ec81a734ccad
o-nikolas
added a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
May 29, 2025
The executor class was being loaded to check if the executor in question supports pickling. However, pickling was removed in apache#43667 but the class ref was left behind. This PR removes it.
hussein-awala
pushed a commit
that referenced
this pull request
May 30, 2025
The executor class was being loaded to check if the executor in question supports pickling. However, pickling was removed in #43667 but the class ref was left behind. This PR removes it.
sanederchik
pushed a commit
to sanederchik/airflow
that referenced
this pull request
Jun 7, 2025
The executor class was being loaded to check if the executor in question supports pickling. However, pickling was removed in apache#43667 but the class ref was left behind. This PR removes it.
jose-lehmkuhl
pushed a commit
to jose-lehmkuhl/airflow
that referenced
this pull request
Jul 11, 2025
The executor class was being loaded to check if the executor in question supports pickling. However, pickling was removed in apache#43667 but the class ref was left behind. This PR removes it.
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this pull request
Sep 23, 2025
Follow-up of apache/airflow#43667 GitOrigin-RevId: 5241132a914b4cd4879f6b44ac28ec81a734ccad
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this pull request
Oct 20, 2025
Follow-up of apache/airflow#43667 GitOrigin-RevId: 5241132a914b4cd4879f6b44ac28ec81a734ccad
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
airflow3.0:breaking
Candidates for Airflow 3.0 that contain breaking changes
area:API
Airflow's REST/HTTP API
area:CLI
area:db-migrations
PRs with DB migration
area:Executors-core
LocalExecutor & SequentialExecutor
area:Scheduler
including HA (high availability) scheduler
area:serialization
area:task-execution-interface-aip72
AIP-72: Task Execution Interface (TEI) aka Task SDK
area:UI
Related to UI/UX. For Frontend Developers.
legacy api
Whether legacy API changes should be allowed in PR
legacy ui
Whether legacy UI change should be allowed in PR
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was a less used part of Airflow and does not make sense to keep it since we are removing DB access as part of AIP-72, I am removing it here. This was missed in Airflow 2.0!
TODO
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.