flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4271) There is no way to set parallelism of operators produced by CoGroupedStreams
Date Wed, 03 Aug 2016 09:31:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405623#comment-15405623

ASF GitHub Bot commented on FLINK-4271:

Github user StephanEwen commented on the issue:

    We should not change the checker sensitivity. It is very important that it checks for
binary compatibility - that was the promise of Flink 1.0.
    If we want to break compatibility, we can define an exception rule to the checker.
    I think we should explore other options before. We can specify the parallelism between
`window(...)` and `apply(...)` without breaking the compatibility. It would be a bit less
nice, because it is different from how the other functions do it, but it allows us to maintain
the promise of compatibility.
    What do you think about that?

> There is no way to set parallelism of operators produced by CoGroupedStreams
> ----------------------------------------------------------------------------
>                 Key: FLINK-4271
>                 URL: https://issues.apache.org/jira/browse/FLINK-4271
>             Project: Flink
>          Issue Type: Bug
>          Components: DataStream API
>            Reporter: Wenlong Lyu
>            Assignee: Jark Wu
> Currently, CoGroupStreams package the map/keyBy/window operators with a human friendly
interface, like: dataStreamA.cogroup(streamB).where(...).equalsTo().window().apply(), both
the intermediate operators and final window operators can not be accessed by users, and we
cannot set attributes of the operators, which make co-group hard to use in production environment.

This message was sent by Atlassian JIRA

View raw message