[ https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730030#comment-14730030 ]
ASF GitHub Bot commented on IGNITE-1370: ---------------------------------------- GitHub user raulk opened a pull request: https://github.com/apache/ignite/pull/67 IGNITE-1370 Streamers: Implement multiple tuple extractor. Added also a unit test in SocketStreamerSelfTest. You can merge this pull request into a Git repository by running: $ git pull https://github.com/raulk/incubator-ignite ignite-1.4 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/67.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #67 ---- commit 36467a027fa95ba6587ada721155e1d0479e1808 Author: Raul Kripalani <ra...@apache.org> Date: 2015-09-03T22:31:08Z IGNITE-1370 Streamers: Implement multiple tuple extractor. ---- > StreamTupleExtractor should allow extracting multiple tuples from a single > event > -------------------------------------------------------------------------------- > > Key: IGNITE-1370 > URL: https://issues.apache.org/jira/browse/IGNITE-1370 > Project: Ignite > Issue Type: Improvement > Components: streaming > Affects Versions: ignite-1.4 > Reporter: Raúl Kripalani > Assignee: Raúl Kripalani > > Currently the {{StreamTupleExtractor}} interface contains a single method: > {code} > public Map.Entry<K, V> extract(T msg); > {code} > Which only allows extracting a single Entry from an incoming event. > In real life, it could be that an event contains multiple entries. -- This message was sent by Atlassian JIRA (v6.3.4#6332)