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-1870) Reintroduce Indexed reader functionality to streaming
Date Fri, 08 Jan 2016 16:15:39 GMT

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

ASF GitHub Bot commented on FLINK-1870:
---------------------------------------

Github user StephanEwen commented on the pull request:

    https://github.com/apache/flink/pull/1483#issuecomment-170044112
  
    The user code should not deal with what channel an element came from. It wires assumptions
about the parallelism of the predecessor into the user code. Adjustments of the parallelism
become impossible that way.
    
    Why does the storm compatibility need this?


> Reintroduce Indexed reader functionality to streaming
> -----------------------------------------------------
>
>                 Key: FLINK-1870
>                 URL: https://issues.apache.org/jira/browse/FLINK-1870
>             Project: Flink
>          Issue Type: Task
>          Components: Streaming
>            Reporter: Gyula Fora
>            Assignee: Matthias J. Sax
>            Priority: Minor
>
> The Indexed record reader classes (IndexedReaderIterator, IndexedMutableReader) were
introduced to allow the streaming operators to access the index of the last read channel from
the input gate. This was a necessary step toward future input sorting operators.
> Unfortunately this untested feature was patched away by the following commit:
> https://github.com/apache/flink/commit/5232c56b13b7e13e2cf10dbe818c221f5557426d
> At some point we need to reimplement these features with proper tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message