Skip to content

Conversation

@kaxil
Copy link
Member

@kaxil kaxil commented Nov 4, 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!

TODO

  • Handle it for Celery & Kubernetes Executors

^ 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.

@kaxil kaxil added the area:task-execution-interface-aip72 AIP-72: Task Execution Interface (TEI) aka Task SDK label Nov 4, 2024
@boring-cyborg 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 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
jedcunningham previously approved these changes Nov 4, 2024
@jedcunningham 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!

@kaxil
Copy link
Member Author

kaxil commented Nov 4, 2024

@jedcunningham Done now :) - c6505d7

@kaxil kaxil added the legacy ui Whether legacy UI change should be allowed in PR label Nov 4, 2024
@kaxil kaxil force-pushed the remove-pickling branch 2 times, most recently from f998628 to 4464668 Compare November 4, 2024 23:38
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 kaxil merged commit b9b0614 into apache:main Nov 5, 2024
@kaxil kaxil deleted the remove-pickling branch November 5, 2024 09:06
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
kaxil added a commit to astronomer/airflow that referenced this pull request Nov 12, 2024
kaxil added a commit to astronomer/airflow that referenced this pull request Nov 12, 2024
kaxil added a commit to astronomer/airflow that referenced this pull request Nov 12, 2024
kaxil added a commit that referenced this pull request Nov 12, 2024
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
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

Development

Successfully merging this pull request may close these issues.

2 participants