Skip to content

Add Dag run context fields to the Java SDK Context#69100

Draft
FrankYang0529 wants to merge 1 commit into
apache:mainfrom
FrankYang0529:airflow-java-context
Draft

Add Dag run context fields to the Java SDK Context#69100
FrankYang0529 wants to merge 1 commit into
apache:mainfrom
FrankYang0529:airflow-java-context

Conversation

@FrankYang0529

@FrankYang0529 FrankYang0529 commented Jun 28, 2026

Copy link
Copy Markdown
Member

The Java SDK's Context only exposed dagId and runId from the Dag run, even though the supervisor already delivers the full run context in the same StartupDetails that Python tasks receive. Add fields logicalDate, dataIntervalStart / dataIntervalEnd, runAfter, ds, runType, and conf to Context.


Was generative AI tooling used to co-author this PR?
  • Yes - Claude Code with Opus 4.8

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

Java tasks could only read the dag id and run id from Context, even though the
supervisor already sends the full run context (logical date, data interval, run
type, trigger conf) in StartupDetails.

Signed-off-by: PoAn Yang <payang@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant