weiqingy opened a new pull request, #30055:
URL: https://github.com/apache/flink/pull/30055

   ## What is the purpose of the change
   
   Backport of #29908 to release-2.4. `EARLY_FIRE` is a streaming interval-join 
hint. With this change, batch mode ignores it, as the docs describe, so a batch 
query with the hint plans exactly as it would without it and keeps adaptive 
broadcast join. The docs also describe the query-block scope of the hint and 
how an early-fire join combines with a downstream interval join. Having this in 
2.4.0 lets users share one query between streaming and batch jobs from the 
first release with the hint.
   
   ## Brief change log
   
     - Cherry-pick of 73bbab71ad4, applied without conflicts
   
   ## Verifying this change
   
   This change added tests: `plan/hints/batch/EarlyFireJoinHintTest`. It, the 
streaming `EarlyFireJoinHintTest`, the other batch join hint tests and 
`AdaptiveJoinTest` pass on this branch.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? docs
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Code 2.1.329 (Claude Opus 5.5)
   


-- 
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]

Reply via email to