Repository navigation
Java SDK: Rewrite the user docs around Dag definition - #74701
Conversation
6cf0e4f to
bd256f1
Compare
FrankYang0529
left a comment
There was a problem hiding this comment.
Thanks for the PR. Leave some comments.
jason810496
left a comment
There was a problem hiding this comment.
Thanks for the review.
c75ec90 to
dc14053
Compare
dc14053 to
c289b5a
Compare
c289b5a to
b6f358f
Compare
Reorder the Java SDK guide to start from a Dag defined in Java, document conditions, switches and TriggerDagRun, and add a table of how stub task arguments bind. Split the README into a user landing page and DEVELOPMENT.md, and add an example README. Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Set the queue once on the Dag in every example, now that a Java Dag takes one, and bump the documented version to 1.0.0-beta2 everywhere. Add a prek hook that fails when the guide, the README and the Dokka landing page name different versions. Restore the TaskInput constraints, correct the LocalExecutor wording, and drop the Python Label comparison. Co-Authored-By: Claude <noreply@anthropic.com>
The quick start appears on three pages. The guide owns it now, between SHARED SNIPPET markers, and the sync-java-sdk-docs hook copies it into the other two and still checks that all three install the same version. Co-Authored-By: Claude <noreply@anthropic.com>
The three pages that show how to install the SDK pinned a release that is not out yet, which also held the PR back. They now install `<version>` and link to Maven Central, and the sync hook fails when a page names a release instead. The parse-failure bullet leads with the SDK release a JAR was built with, and keeps the supervisor schema version as the explanation. Co-Authored-By: Claude <noreply@anthropic.com>
b6f358f to
1b80207
Compare
Backport failed to create: v3-4-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker a419633 v3-4-testThis should apply the commit to the v3-4-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 --continueIf you don't have cherry-picker installed, see the installation guide. |
Why
The Java SDK guide started from stub tasks of a Python Dag and did not cover conditions, switches or
TriggerDagRun, and the README mixed user docs with the contributor and release guide.What
java.rst: rewrite it in the same order as the TypeScript guide.@Airflow.If/dag.If,@Airflow.Switch/dag.SwitchandTriggerDagRun.Clientmethods and the logging integrations.java-sdk/README.md: keep installation, a quick start, links to the guide and the compatibility matrix.java-sdk/DEVELOPMENT.md: new, holding the build, release and contributing content moved from the README. References to it are updated.java-sdk/example/README.md: new, listing the example Dags under "Dag definition" and "Python Dag with stub TaskHandler".java-sdk/sdk/module.md(API reference landing page): add a quick start.Was generative AI tooling used to co-author this PR?