You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2022/06/10 07:49:00 UTC

[jira] [Updated] (FLINK-27992) cep StreamExecMatch need check the parallelism and maxParallelism of the two transformation in it

     [ https://issues.apache.org/jira/browse/FLINK-27992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Visser updated FLINK-27992:
-----------------------------------
    Fix Version/s:     (was: 1.16.0)

> 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: Improvement
>          Components: Library / CEP
>    Affects Versions: 1.16.0
>            Reporter: jackylau
>            Priority: Major
>
> 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.7#820007)