[hotfix][table-runtime] Fix typo in RowTimeMiniBatchAssignerOperator class name

[Dennis-Mircea]

What is the purpose of the change

This pull request fixes a typo in the class name RowTimeMiniBatchAssginerOperator. The class is renamed to RowTimeMiniBatchAssignerOperator (and the corresponding test class to RowTimeMiniBatchAssignerOperatorTest), matching the spelling already used by its sibling ProcTimeMiniBatchAssignerOperator and the surrounding package wmassigners.

The class is @Internal (it is an implementation-side stream operator with no stability annotation, instantiated only by the table planner) and holds no operator/keyed state, so the rename is safe to do directly.

Brief change log

• Rename RowTimeMiniBatchAssginerOperator → RowTimeMiniBatchAssignerOperator (file, class, and constructor) in flink-table-runtime.
• Rename the matching test class RowTimeMiniBatchAssginerOperatorTest → RowTimeMiniBatchAssignerOperatorTest.
• Update the only two callers/references: StreamExecMiniBatchAssigner (flink-table-planner) and the {@link ...} reference in the javadoc of ProcTimeMiniBatchAssignerOperator.

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

The existing tests in RowTimeMiniBatchAssignerOperatorTest continue to pass under the renamed class:

./mvnw -pl flink-table/flink-table-runtime -Dtest='RowTimeMiniBatchAssignerOperatorTest' test

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 class is internal; it has no stability annotation and is only instantiated from StreamExecMiniBatchAssigner)
• The serializers: no
• The runtime per-record code paths (performance sensitive): no (identifier-only change, no behavior change)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no (the operator carries only transient runtime fields and a final config value, no operator/keyed state)
• 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

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

[flinkbot]

CI report:

• 8ccec5d Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[spuru9]

Thanks for the fix.

[raminqaf]

Thanks for fixing this!

[davidradl]

This is a change to the API - can see this in the java docs https://nightlies.apache.org/flink/flink-docs-stable/api/java/overview-tree.html
I suggest you deprecate the existing one and introduce the newly correctly named one. Then there will be no migration impact.

[Dennis-Mircea]

This is a change to the API - can see this in the java docs https://nightlies.apache.org/flink/flink-docs-stable/api/java/overview-tree.html I suggest you deprecate the existing one and introduce the newly correctly named one. Then there will be no migration impact.

Thanks for taking a look! I don't think this operator is part of the public API surface, though:

• It lives in flink-table-runtime, an implementation module. The public API surfaces in Flink are flink-core-api, flink-datastream-api, and flink-table-api-java.
• It carries no @Public / @PublicEvolving / @Experimental annotation. The sibling classes in the same package (PeriodicWatermarkAssignerWrapper, PunctuatedWatermarkAssignerWrapper) are explicitly @Internal.
• It is only ever instantiated by the planner (StreamExecMiniBatchAssigner), and users don't construct it directly.
• The Flink Javadoc tree lists every public-visibility class, including @Internal ones, so presence there isn't evidence of API status.

Given that, a typo fix via rename should be safe and keeping a deprecated misspelled shim would just be carrying a misleading class name forward. Please let me know if I'm missing something.