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-2279) Allow treating iteration head as ConnectedDataStream
Date Fri, 26 Jun 2015 16:44:05 GMT

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

ASF GitHub Bot commented on FLINK-2279:

Github user aljoscha commented on the pull request:

    This looks reasonable. How does the user not specify which elements are feedback and which
go to the downstream operator?

> Allow treating iteration head as ConnectedDataStream 
> -----------------------------------------------------
>                 Key: FLINK-2279
>                 URL: https://issues.apache.org/jira/browse/FLINK-2279
>             Project: Flink
>          Issue Type: New Feature
>          Components: Streaming
>    Affects Versions: 0.10
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Minor
> Currently the streaming iterations are restricted to use the same input and feedback
types which are routed through the same operator.
> This means that if the user want to distinguish between normal input and feedback record
he/she needs to mark it somehow and also a wrapper type is necessary for handling separate
input and feedback types.
> This makes implementing iterative algorithms (such as ML) quite ugly at some points.
> I propose to let the user treat the normal input if the iteration head operator and the
feedback input as a ConnectedDataStream which can be used to apply co-operators both distinguishing
the inputs and allowing different feedback types for elegant implementations.

This message was sent by Atlassian JIRA

View raw message