[
https://issues.apache.org/jira/browse/FLINK-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101611#comment-15101611
]
ASF GitHub Bot commented on FLINK-1870:
---------------------------------------
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1483#issuecomment-171931389
I think that the Storm compatibility layer is very important. I also think,
however, that when making decisions about whether to enhance to core API to
serve other APIs or making that other API jump through some hoops then the
cleanliness of the core API should be favored if possible.
> 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)
