[
https://issues.apache.org/jira/browse/FLINK-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101687#comment-15101687
]
ASF GitHub Bot commented on FLINK-1870:
---------------------------------------
Github user mjsax commented on the pull request:
https://github.com/apache/flink/pull/1483#issuecomment-171944496
With embedded mode, I mean to use a spout/bolt within a regular Flink
streaming program. For this, you could even have a "plain/raw" input stream
(eg, `DataStream<String>`) or a POJO. Both can be translated into StormTuple
(which is only used for input tuples). Output tuples are of type `Values` and
also translated back to `TupleX` type.
Extending the tuples with an additional field would work, too. But I did
not like this, because is increases the data that need to be shipped over the
network. For embedded mode, we would need to think of a nice "work around" for
"plain/raw" and POJO input streams -- but this should not be a problem. As
there are no globally unique task-ids anyway in embedded mode, it might be even
ok not to support this feature...
I personally do not see it as a big (very dangerous) problem in exposing
"input channel index" to the operators. But if you are strictly against it, I
will go with the "additional field" approach to provide this information.
> 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)
