[
https://issues.apache.org/jira/browse/FLINK-27992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808230#comment-17808230
]
Dawid Wysakowicz commented on FLINK-27992:
------------------------------------------
Both operators use the same parallelism. Match uses the parallelism of the
input. There is a different issue though that Match uses
`ChainingStrategy.HEAD` which puts `StreamRecordInserter` and `Match` into
separate chains adding unwanted `FORWARD` exchange.
> cep StreamExecMatch need check the parallelism and maxParallelism of the two
> transformation in it
> -------------------------------------------------------------------------------------------------
>
> Key: FLINK-27992
> URL: https://issues.apache.org/jira/browse/FLINK-27992
> Project: Flink
> Issue Type: Bug
> Components: Library / CEP
> Affects Versions: 1.16.0
> Reporter: Jacky Lau
> Assignee: Dawid Wysakowicz
> Priority: Blocker
> Labels: pull-request-available
>
> StreamExecMatch node has two transformation (StreamRecordTimestampInserter ->
> Match), the upstream of StreamExecMatch is hash edge when use set different
> parallelism and maxParallelism it will cause problem.
> because the window operator using downstream node's max parallelism compute
> keygroup and cep operator using max parallelism of itself and it may not
> equal
> such as:
> window - --(hash edge)> StreamRecordTimestampInserter --(forward edge)–> Cep
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
