[ https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738440#comment-14738440 ]
Raúl Kripalani commented on IGNITE-1370: ---------------------------------------- If you duplicate them, the user won't be able to use both interfaces interchangeably. Hence, I think extension is more comfortable for the user at this point. We also want to rename the field in {{extractor}} field in {{StreamAdapter}} to {{singleTupleExtractor}}, creating new getters and setters but keeping the old ones {{getExtractor}} and {{setExtractor}} and marking them as {{@Deprecated}}. Raúl. > 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)