[
https://issues.apache.org/jira/browse/FLINK-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413641#comment-15413641
]
ASF GitHub Bot commented on FLINK-4271:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2305
I just thought of a different trick: We could add a second variant of the
`apply(..)` function (for example called `with(...)` as in the DataSet API) and
have the proper return type there (calling apply() and cast).
We can then immediately deprecate the `with()` function to indicate that it
is a temporary workaround and is to be replaced by `apply(...)` in Flink 2.0.
> 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)
