Repository navigation
Java SDK: Send log timestamps in UTC - #74783
Merged
jason810496 merged 2 commits intoOct 20, 2026
Merged
Conversation
jason810496
reviewed
Oct 19, 2026
FrankYang0529
force-pushed
the
fix-java-sdk-log-timestamp-utc
branch
from
October 19, 2026 15:10
524a8aa to
ee37cfa
Compare
FrankYang0529
force-pushed
the
fix-java-sdk-log-timestamp-utc
branch
from
October 20, 2026 02:15
ee37cfa to
d73ccb5
Compare
Signed-off-by: PoAn Yang <payang@apache.org>
Signed-off-by: PoAn Yang <payang@apache.org>
jason810496
approved these changes
Oct 20, 2026
jason810496
left a comment
Member
There was a problem hiding this comment.
LGTM once we address the final comment, thanks.
FrankYang0529
force-pushed
the
fix-java-sdk-log-timestamp-utc
branch
from
October 20, 2026 03:33
d73ccb5 to
8c0e67c
Compare
jason810496
approved these changes
Oct 20, 2026
Contributor
Backport successfully created: v3-4-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
vatsrahul1001
pushed a commit
that referenced
this pull request
Oct 20, 2026
* Java SDK: Send log timestamps in UTC * Fix Java SDK log time zone and a supervisor crash on bad timestamps --------- (cherry picked from commit 9091cd0) Signed-off-by: PoAn Yang <payang@apache.org> Co-authored-by: PoAn Yang <payang@apache.org>
vatsrahul1001
pushed a commit
that referenced
this pull request
Oct 20, 2026
* Java SDK: Send log timestamps in UTC * Fix Java SDK log time zone and a supervisor crash on bad timestamps --------- (cherry picked from commit 9091cd0) Signed-off-by: PoAn Yang <payang@apache.org> Co-authored-by: PoAn Yang <payang@apache.org>
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
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.
Why
timestampof each log record as the JVM's local time without a UTC offset. Airflow reads a timestamp without an offset as a time in[core] default_timezone, which is UTC by default. A user not in default timezone will get unexpected log time.LocalDateTime.toString()leaves out the seconds on a whole minute, for example2026-10-13T17:41. The supervisor cannot parse that string, so it stops before it reports the task's final state.How
LogMessage.timestampis ajava.time.Instant, andLogSendersends the result ofInstant.toString(). That string is in UTC, ends withZ, and always includes the seconds.DecodeErrorwhen it cannot parse atimestamp. It moves the value toinvalid_timestampand stamps the line with its arrival time.Was generative AI tooling used to co-author this PR?