[ https://issues.apache.org/jira/browse/FLINK-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426214#comment-15426214 ]
ASF GitHub Bot commented on FLINK-4271: --------------------------------------- Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/2305 +1 for this approach. On Thu, Aug 18, 2016 at 6:59 AM, Jark <notificati...@github.com> wrote: > I'm ok with the with(...) approach. In addition, we should create a JIRA > under [FLINK-3957] > "Breaking API changes for Flink 2.0", to keep track of deprecating and > changing the apply method return type. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/flink/pull/2305#issuecomment-240624274>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AFfXul4OQ2wEhcdMXC3_gqtZ-zqEIV6Kks5qg-bNgaJpZM4JW9go> > . > > 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)