Repository navigation
[v3-4-test] Java SDK: Let a native Java Dag set one queue for all its tasks (#74538) - #75402
Open
github-actions[bot] wants to merge 2 commits into
Open
github-actions[bot] wants to merge 2 commits into
github-actions[bot] wants to merge 2 commits into
Conversation
… tasks (#74538) * Java SDK: Let a native Java Dag set one queue for all its tasks Every task of a native Java Dag runs on the Java coordinator, so each one needs a queue that queue_to_coordinator routes there. Airflow's Dag has no queue setting, so authors had to repeat the same queue on every task. The Go and TypeScript SDKs already take a Dag-level queue that each task inherits unless it sets its own; this gives Java the same. * Reject a blank Dag-level queue and fix the native Dag queue docs A blank queue matched no coordinator, so every task stayed queued. The parsing docs still said there was no Dag-level queue and routed a queue the examples do not use. * Reject a blank Dag-level queue in the annotation processor * Carry the blank rule on the schema field, for Dag and task queues alike * Set the queue once per Dag in the e2e native bundle * Put the blank check on Field and tidy the comments --------- (cherry picked from commit fc9c4b0) Co-authored-by: Jason(Zhe-You) Liu <68415893+jason810496@users.noreply.github.com>
1 task done
jason810496
approved these changes
Oct 22, 2026
jason810496
marked this pull request as ready for review
October 22, 2026 12:39
jason810496
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jscheffl,
potiuk and
uranusjr
as code owners
October 22, 2026 12:39
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Every task of a native Java Dag runs on the Java coordinator, so each one
needs a queue that queue_to_coordinator routes there. Airflow's Dag has no
queue setting, so authors had to repeat the same queue on every task. The
Go and TypeScript SDKs already take a Dag-level queue that each task
inherits unless it sets its own; this gives Java the same.
A blank queue matched no coordinator, so every task stayed queued.
The parsing docs still said there was no Dag-level queue and routed a
queue the examples do not use.
Reject a blank Dag-level queue in the annotation processor
Carry the blank rule on the schema field, for Dag and task queues alike
Set the queue once per Dag in the e2e native bundle
Put the blank check on Field and tidy the comments
(cherry picked from commit fc9c4b0)
Co-authored-by: Jason(Zhe-You) Liu 68415893+jason810496@users.noreply.github.com