-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
AIP-72: Remove DAG pickling #43667
Merged
Merged
AIP-72: Remove DAG pickling #43667
Conversation
This file contains 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
kaxil
added
the
area:task-execution-interface-aip72
AIP-72: Task Execution Interface (TEI) aka Task SDK
label
Nov 4, 2024
kaxil
requested review from
bbovenzi,
pierrejeambrun,
ryanahamilton,
jscheffl,
ashb,
ephraimbuddy,
potiuk,
jedcunningham,
bolkedebruin,
XD-DENG,
o-nikolas and
hussein-awala
as code owners
November 4, 2024 22:29
boring-cyborg
bot
added
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:UI
Related to UI/UX. For Frontend Developers.
labels
Nov 4, 2024
kaxil
added
airflow3.0:breaking
Candidates for Airflow 3.0 that contain breaking changes
legacy api
Whether legacy API changes should be allowed in PR
labels
Nov 4, 2024
jedcunningham
previously approved these changes
Nov 4, 2024
jedcunningham
dismissed
their stale review
November 4, 2024 22:37
Oh, actually, going to wait until KE & CE are done :) But so far looks good!
@jedcunningham Done now :) - c6505d7 |
jedcunningham
approved these changes
Nov 4, 2024
kaxil
force-pushed
the
remove-pickling
branch
2 times, most recently
from
November 4, 2024 23:38
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!
kaxil
force-pushed
the
remove-pickling
branch
from
November 5, 2024 00:32
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
LefterisXefteris
pushed a commit
to LefterisXefteris/airflow
that referenced
this pull request
Jan 5, 2025
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.rst
or{issue_number}.significant.rst
, in newsfragments.