[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729884#comment-14729884
]
Raúl Kripalani commented on IGNITE-1370:
----------------------------------------
There are two options off the top of my head:
# API-breaking one => modifying StreamTupleExtractor to add a second method
returning a Map<K, V> and a method {{boolean supportsMultiple()}} for users to
implement, so that Streamers can query the extractor to know which method to
invoke.
# A new class {{StreamMultipleTupleExtractor}} that Streamers supporting this
functionality can use. It would require streamers to hold two fields:
singleTupleExtractor or multipleTupleExtractor (for example), for users to be
able to set either.
> 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)
