beyond1920 opened a new pull request #16408:
URL: https://github.com/apache/flink/pull/16408
…WindowAggregateOnUpsertSource
<!--
*Thank you very much for contributing to Apache Flink - we are happy that
you want to help us improve Flink. To help the community review your
contribution in the best possible way, please go through the checklist below,
which will get the contribution into a shape in which it can be best reviewed.*
*Please understand that we do not do this to make contributions to Flink a
hassle. In order to uphold a high standard of quality for code contributions,
while at the same time managing a large number of contributions, we need
contributors to prepare the contributions well, and give reviewers enough
contextual information for the review. Please also understand that
contributions that do not follow this guide will take longer to review and thus
typically be picked up with lower priority by the community.*
## Contribution Checklist
## What is the purpose of the change
The pr aims to fix unstable itcases
`GroupWindowITCase#testWindowAggregateOnUpsertSource`.
The unstable case is caused by whether the last two records dropped as late
data is nonderterministic. It depends on the watermark on current task which is
relates to what data is processed and the order of incoming data on each
concurrent task.
And `GroupWindowITCase#testWindowAggregateOnUpsertSourcePushdownWatermark`
has similar problems, I would set parallelism to 1 for those two cases to avoid
unstable failure.
## Brief change log
- Update Itcase
`GroupWindowITCase#testWindowAggregateOnUpsertSourcePushdownWatermark` and
`GroupWindowITCase#testWindowAggregateOnUpsertSource` to set parallellism to 1.
## Verifying this change
- Existed ITCase
## 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)
--
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]
