Skip to content

Conversation

@SteveStevenpoor
Copy link
Contributor

What is the purpose of the change

This pull request introduces integration tests for MultiJoin operator.

Brief change log

  • MultiJoinItCase added to flink table planner

Verifying this change

This change added tests and can be verified as follows:

  • Added integration tests with parallelism > 1 to test MultiJoin functionality in such scenario
  • Expected results were created by turning TABLE_OPTIMIZER_MULTI_JOIN_ENABLED off

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? not applicable

@flinkbot
Copy link
Collaborator

flinkbot commented Jan 14, 2026

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

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.

2 participants