[
https://issues.apache.org/jira/browse/FLINK-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425006#comment-15425006
]
ASF GitHub Bot commented on FLINK-4271:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2305
I would like to come to an agreement with everyone how to proceed.
From the discussion on the mailing list, I see that quite some people are
opposed to breaking the compatibility unless we name the next release 2.0.
Since that has not been decided upon, we need a different fix.
How about we introduce (and immediately deprecate) the `with(...)` method.
We should describe there that this is a temporary workaround. The `with(...)
method only differs in the return type and calls `apply(...)`, casting the
returned value.
Would everyone be okay with 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
(v6.3.4#6332)
