-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Move TaskGroup UI & API functions to server-side
#54857
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
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
kaxil
commented
Aug 23, 2025
kaxil
commented
Aug 23, 2025
task_group_to_dict functions to CoreTaskGroup UI & API functions to server-side
5fb25f5 to
0ee9b2c
Compare
ashb
reviewed
Aug 23, 2025
…organize tests Follow-up of the fix in apache#54756 - Move `task_group_to_dict` and `task_group_to_dict_grid` functions from `task-sdk` to `airflow-core` API services - Update import paths in `grid.py` and `structure.py` to use new server-side location - Update deprecation mappings to point to new FastAPI service module locations - Remove `AbstractOperator` from isinstance checks in server-side functions (now handles only serialized objects) - Split mixed tests: moved TaskGroup functionality tests to `task-sdk`, keep server function tests in `airflow-core` - Add comprehensive TaskGroup tests in `task-sdk` covering creation, relationships, decorators, and validation - Create clear architectural boundary: client-side TaskGroup authoring vs server-side serialized DAG processing
0ee9b2c to
fb0c242
Compare
ashb
approved these changes
Aug 26, 2025
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker c8a0f51 v3-0-testThis should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
mangal-vairalkar
pushed a commit
to mangal-vairalkar/airflow
that referenced
this pull request
Aug 30, 2025
…organize tests (apache#54857) Follow-up of the fix in apache#54756 - Move `task_group_to_dict` and `task_group_to_dict_grid` functions from `task-sdk` to `airflow-core` API services - Update import paths in `grid.py` and `structure.py` to use new server-side location - Update deprecation mappings to point to new FastAPI service module locations - Remove `AbstractOperator` from isinstance checks in server-side functions (now handles only serialized objects) - Split mixed tests: moved TaskGroup functionality tests to `task-sdk`, keep server function tests in `airflow-core` - Add comprehensive TaskGroup tests in `task-sdk` covering creation, relationships, decorators, and validation - Create clear architectural boundary: client-side TaskGroup authoring vs server-side serialized DAG processing
nothingmin
pushed a commit
to nothingmin/airflow
that referenced
this pull request
Sep 2, 2025
…organize tests (apache#54857) Follow-up of the fix in apache#54756 - Move `task_group_to_dict` and `task_group_to_dict_grid` functions from `task-sdk` to `airflow-core` API services - Update import paths in `grid.py` and `structure.py` to use new server-side location - Update deprecation mappings to point to new FastAPI service module locations - Remove `AbstractOperator` from isinstance checks in server-side functions (now handles only serialized objects) - Split mixed tests: moved TaskGroup functionality tests to `task-sdk`, keep server function tests in `airflow-core` - Add comprehensive TaskGroup tests in `task-sdk` covering creation, relationships, decorators, and validation - Create clear architectural boundary: client-side TaskGroup authoring vs server-side serialized DAG processing
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:dev-tools
area:task-sdk
backport-to-v3-1-test
Mark PR with this label to backport to v3-1-test branch
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.
Follow-up of the fix in #54756
task_group_to_dictandtask_group_to_dict_gridfunctions fromtask-sdktoairflow-coreAPI servicesgrid.pyandstructure.pyto use new server-side locationAbstractOperatorfrom isinstance checks in server-side functions (now handles only serialized objects)task-sdk, keep server function tests inairflow-coretask-sdkcovering creation, relationships, decorators, and validation^ 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 airflow-core/newsfragments.