Skip to content

Conversation

@kaxil
Copy link
Member

@kaxil kaxil commented Mar 25, 2025

closes #45743

I am not touching Providers (to change import Path for BaseSensorOperator) in this PR since I might move BaseOperator and BaseSensorOperator under airflow.sdk.bases module since they aren't really needed for DAG Authors.

Future Work:

@kaxil kaxil force-pushed the move-basop-sdk branch 7 times, most recently from 5f7eb7f to e33ea1b Compare March 26, 2025 22:26
@kaxil kaxil marked this pull request as ready for review March 26, 2025 22:26
@kaxil kaxil requested a review from eladkal as a code owner March 26, 2025 23:54
@kaxil kaxil force-pushed the move-basop-sdk branch 2 times, most recently from 03e1959 to a22d544 Compare March 27, 2025 12:20
kaxil added a commit to astronomer/airflow that referenced this pull request Mar 27, 2025
As we are replacing BaseOperator usage from Core to Task SDK, we are running into several issues, one of the common one being over-usage of `task.run()`.

While some cases can be easily replaced by `task.execute()` others needs execution of the tasks, sharing of XCom's in between, checking task state, correct exception etc.

To make this easier I have added `run_task` fixture which I have been using in apache#48244 and it has worked out well.

Example:
kaxil added a commit that referenced this pull request Mar 27, 2025
As we are replacing BaseOperator usage from Core to Task SDK, we are running into several issues, one of the common one being over-usage of `task.run()`.

While some cases can be easily replaced by `task.execute()` others needs execution of the tasks, sharing of XCom's in between, checking task state, correct exception etc.

To make this easier I have added `run_task` fixture which I have been using in #48244 and it has worked out well.

Example:
@kaxil kaxil force-pushed the move-basop-sdk branch 2 times, most recently from 44e4328 to e0b0458 Compare March 27, 2025 17:14
@kaxil kaxil requested a review from o-nikolas as a code owner March 27, 2025 17:14
@kaxil kaxil force-pushed the move-basop-sdk branch 3 times, most recently from 2c5ee02 to 465594b Compare March 27, 2025 19:53
@kaxil kaxil force-pushed the move-basop-sdk branch 2 times, most recently from 7cdfa3c to cfed275 Compare March 27, 2025 21:00
Copy link
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

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

I do not have any major concerns the way things have been done, a few nits here are there

Copy link
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

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

Missed approving!

@kaxil kaxil merged commit 347c98c into apache:main Mar 28, 2025
89 checks passed
@kaxil kaxil deleted the move-basop-sdk branch March 28, 2025 07:58
pankajkoti pushed a commit to astronomer/airflow that referenced this pull request Mar 28, 2025
As we are replacing BaseOperator usage from Core to Task SDK, we are running into several issues, one of the common one being over-usage of `task.run()`.

While some cases can be easily replaced by `task.execute()` others needs execution of the tasks, sharing of XCom's in between, checking task state, correct exception etc.

To make this easier I have added `run_task` fixture which I have been using in apache#48244 and it has worked out well.

Example:
pankajkoti pushed a commit to astronomer/airflow that referenced this pull request Mar 28, 2025
shubham-pyc pushed a commit to shubham-pyc/airflow that referenced this pull request Apr 2, 2025
As we are replacing BaseOperator usage from Core to Task SDK, we are running into several issues, one of the common one being over-usage of `task.run()`.

While some cases can be easily replaced by `task.execute()` others needs execution of the tasks, sharing of XCom's in between, checking task state, correct exception etc.

To make this easier I have added `run_task` fixture which I have been using in apache#48244 and it has worked out well.

Example:
shubham-pyc pushed a commit to shubham-pyc/airflow that referenced this pull request Apr 2, 2025
nailo2c pushed a commit to nailo2c/airflow that referenced this pull request Apr 4, 2025
As we are replacing BaseOperator usage from Core to Task SDK, we are running into several issues, one of the common one being over-usage of `task.run()`.

While some cases can be easily replaced by `task.execute()` others needs execution of the tasks, sharing of XCom's in between, checking task state, correct exception etc.

To make this easier I have added `run_task` fixture which I have been using in apache#48244 and it has worked out well.

Example:
nailo2c pushed a commit to nailo2c/airflow that referenced this pull request Apr 4, 2025
simonprydden pushed a commit to simonprydden/airflow that referenced this pull request Apr 8, 2025
As we are replacing BaseOperator usage from Core to Task SDK, we are running into several issues, one of the common one being over-usage of `task.run()`.

While some cases can be easily replaced by `task.execute()` others needs execution of the tasks, sharing of XCom's in between, checking task state, correct exception etc.

To make this easier I have added `run_task` fixture which I have been using in apache#48244 and it has worked out well.

Example:
simonprydden pushed a commit to simonprydden/airflow that referenced this pull request Apr 8, 2025
kosteev pushed a commit to GoogleCloudPlatform/composer-airflow that referenced this pull request May 28, 2025
As we are replacing BaseOperator usage from Core to Task SDK, we are running into several issues, one of the common one being over-usage of `task.run()`.

While some cases can be easily replaced by `task.execute()` others needs execution of the tasks, sharing of XCom's in between, checking task state, correct exception etc.

To make this easier I have added `run_task` fixture which I have been using in apache/airflow#48244 and it has worked out well.

Example:
GitOrigin-RevId: 80840cb5734630f95d831dd10ae103c3df3a4b2f
kosteev pushed a commit to GoogleCloudPlatform/composer-airflow that referenced this pull request Sep 24, 2025
As we are replacing BaseOperator usage from Core to Task SDK, we are running into several issues, one of the common one being over-usage of `task.run()`.

While some cases can be easily replaced by `task.execute()` others needs execution of the tasks, sharing of XCom's in between, checking task state, correct exception etc.

To make this easier I have added `run_task` fixture which I have been using in apache/airflow#48244 and it has worked out well.

Example:
GitOrigin-RevId: 80840cb5734630f95d831dd10ae103c3df3a4b2f
kosteev pushed a commit to GoogleCloudPlatform/composer-airflow that referenced this pull request Oct 22, 2025
As we are replacing BaseOperator usage from Core to Task SDK, we are running into several issues, one of the common one being over-usage of `task.run()`.

While some cases can be easily replaced by `task.execute()` others needs execution of the tasks, sharing of XCom's in between, checking task state, correct exception etc.

To make this easier I have added `run_task` fixture which I have been using in apache/airflow#48244 and it has worked out well.

Example:
GitOrigin-RevId: 80840cb5734630f95d831dd10ae103c3df3a4b2f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Move BaseSensor out of core and in to TaskSDK definitions

3 participants