Skip to content

[FLINK-34610] Migrate StreamPhysicalLimitRule from Scala to Java#27723

Open
raminqaf wants to merge 1 commit intoapache:masterfrom
raminqaf:FLINK-34610
Open

[FLINK-34610] Migrate StreamPhysicalLimitRule from Scala to Java#27723
raminqaf wants to merge 1 commit intoapache:masterfrom
raminqaf:FLINK-34610

Conversation

@raminqaf
Copy link
Contributor

@raminqaf raminqaf commented Mar 2, 2026

What is the purpose of the change

Part of the migration plan from Scala to Java described in this ticket: https://issues.apache.org/jira/browse/FLINK-34156

Brief change log

Migrate StreamPhysicalLimitRule from Scala to Java

Verifying this change

All the tests should be green and the conversion should not introduce any errors.

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? JavaDocs

@raminqaf raminqaf changed the title [FLINK-34610] Migrate StreamPhysicalLimitRule from Scala to Java [FLINK-34610] Migrate StreamPhysicalLimitRule from Scala to Java Mar 2, 2026
@raminqaf raminqaf changed the title [FLINK-34610] Migrate StreamPhysicalLimitRule from Scala to Java [FLINK-34610] Migrate StreamPhysicalLimitRule from Scala to Java Mar 2, 2026
@flinkbot
Copy link
Collaborator

flinkbot commented Mar 2, 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