[
https://issues.apache.org/jira/browse/FLINK-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098934#comment-15098934
]
ASF GitHub Bot commented on FLINK-1870:
---------------------------------------
Github user mjsax commented on the pull request:
https://github.com/apache/flink/pull/1483#issuecomment-171790057
Ok. I will try to rework this to the custom operator approach...
About your last statement: We could decide to omit this information in the
Storm compatibility layer (and drop this PR completely) -- of course, this
would limits the "compatibility level" we can achieve.
Btw: Storm does not give the "channel index" itself to the user, but the
task-id of the parallel producer task attached to each input tuple (in Storm,
task-ids are unique over all tasks over all operators of the topology). The
compatibility will translate the "channel index" into this task-id (using the
"channel index" is the only way I see to get this done in the compatibility
layer).
> 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)
