[FLINK-40172][table-runtime] Support processing-time early fire on a row-time interval join - #5
Draft
weiqingy wants to merge 1 commit into
Draft
Conversation
weiqingy
force-pushed
the
FLINK-36953-pr5-proctime
branch
from
July 18, 2026 22:12
11edb43 to
8635ad0
Compare
weiqingy
force-pushed
the
FLINK-36953-pr4-runtime
branch
from
July 18, 2026 22:12
a56a787 to
fcb8e67
Compare
weiqingy
changed the title
weiqingy
force-pushed
the
FLINK-36953-pr4-runtime
branch
from
July 21, 2026 02:17
fcb8e67 to
72e92e5
Compare
weiqingy
force-pushed
the
FLINK-36953-pr5-proctime
branch
from
July 21, 2026 02:17
8635ad0 to
23aabdc
Compare
… interval join
Add the cross-domain timer combination the previous commit left out: an
event-time interval join with EARLY_FIRE('time_mode'='proctime') now fires its
speculative pads on the wall clock while keeping its event-time cleanup. The
temporary "not yet supported" rejection in the planner rule is removed; the
row-time-on-processing-time rejection is retained.
onTimer distinguishes the two timer kinds by OnTimerContext.timeDomain(): in
the cross-domain case early-fire timers are processing-time and cleanup timers
are event-time, so a processing-time firing runs early fire and returns while
an event-time firing runs cleanup only. The discrimination is gated on a new
cross-domain flag, so the natural pairings keep the previous timestamp - delay
recovery where early fire and cleanup share a domain.
A processing-time firing timestamp cannot be mapped back to an event-time cache
bucket arithmetically, so a per-side MapState<Long, List<Long>> keyed by firing
processing-time records the event-time bucket keys due to fire then. It is
allocated only in the cross-domain case and reuses the existing per-bucket emit
and positional fired bit, so the retract-and-correct path is shared. Every
scheduled firing time fires and removes its own entry, and a bucket already
cleaned by event-time expiry makes the firing a no-op, so nothing accumulates.
The schedule is value-typed and order-preserving and processing-time timers are
checkpointed, so a timer pending at snapshot fires after restore against the
restored schedule and fired bits and emits at most the not-yet-emitted pad.
Harness tests cover the wall-clock trigger without watermark advance, a snapshot
before the timer fires, and a snapshot after the pad is emitted.
weiqingy
force-pushed
the
FLINK-36953-pr4-runtime
branch
from
July 21, 2026 04:43
72e92e5 to
ebe6e95
Compare
weiqingy
force-pushed
the
FLINK-36953-pr5-proctime
branch
from
July 21, 2026 04:43
23aabdc to
67c13cc
Compare
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
1 participant
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.
Part of the FLIP-497 stack under umbrella FLINK-36953. Stacked on PR-4. Landing order: PR-1a → PR-1b → PR-2 → PR-3 → PR-4 → PR-5 (this) → PR-6 → PR-7.
What is the purpose of the change
Allows an event-time interval join to early-fire on processing time (
time-mode='proctime'). This is the cross-domain combination: the join's window is event-time, but the speculative early-fire is driven by wall-clock timers. The PR removes the temporary "not yet supported" rejection added earlier in the stack.Brief change log
StreamPhysicalIntervalJoinRulerejection ofproctimetriggering on a row-time join.Verifying this change
This change added tests and can be verified as follows:
RowTimeIntervalJoinTest; theIntervalJoinTestproctime-on-rowtime case now plans successfully.Does this pull request potentially affect one of the following parts:
@Public(Evolving): noDocumentation
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Anthropic)