ParyshevSergey opened a new pull request, #23516:
URL: https://github.com/apache/flink/pull/23516
## What is the purpose of the change
Flink SqlMonotonicity doesn't calculated for
Calc/FlinkLogicalCalc/StreamPhysicalCalc that leads of absent correct
monotonicity for projects. GroupAggregate, based on the input data about the
monotonicity of projections make a choice about the need to retract messages.
## Brief change log
Changed logic of calculating SqlMonotonicty for Calc (base class for all
Calc's) in class FlinkRelMdModifiedMonotonicity.
## Verifying this change
org.apache.flink.table.planner.runtime.stream.sql.AggregateITCase#testMaxRetract
org.apache.flink.table.planner.plan.metadata.FlinkRelMdModifiedMonotonicityTest#testMonotonicityWithCondition
## 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 documented)
--
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]
