Andrushika opened a new pull request, #74710: URL: https://github.com/apache/airflow/pull/74710
## Why The Dag processor runs the JAR of a native Java Dag again on every re-parse, and the worker runs the same JAR for each task. So a JAR can build its Dags from a file in the Dag bundle, and changing only that file changes the live Dags with no rebuild. #74636 tests this end to end for Go, but nothing tests it for Java yet. ## What - `DynamicDags` in `java-native-bundle` makes one Dag per entry of the `dags.yaml` next to the JAR. Its task looks up the greeting by Dag ID, because the Java `DagDef` API cannot bind a literal task input. - `test_java_sdk_dynamic_dag.py` runs the same 3 → 5 → 2 Dag swap as the Go test. The swap helper moves out of the Go test into `e2e_test_utils/dynamic_dags.py`, and `java.yml` copies the re-parse settings of `go.yml`. - I put the Dags in the existing native-Dag JAR, not a new bundle, so CI builds no extra Gradle bundle. related: #74636 --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes (please specify the tool below) Generated-by: Claude Code (Claude Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
