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 2024/01/17 14:31:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17807743#comment-17807743 ] 

Martijn Visser commented on FLINK-27992:
----------------------------------------

[~dwysakowicz] I've upgraded this ticket to a Blocker because I think it should be fixed for the next 1.18 patch release, if you disagree feel free to lower it. 

> 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: Jacky Lau
>            Assignee: Dawid Wysakowicz
>            Priority: Blocker
>
> 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)