[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997848#comment-14997848
]
Roman Shtykh commented on IGNITE-1370:
--------------------------------------
Your first design idea (modifying StreamTupleExtractor to add a second method
returning a Map<K, V>) is better for real use cases.
In some cases if you want to initialize a user-specified extractor you have no
knowledge of. For instance, from a configuration file you have to do the
following
{code}
Class<Some_Extractor> clazz =
(Class<Some_Extractor>)Class.forName(tupleExtractorCls);
then create new instance
{code}
What should be Some_Extractor? Single or multiple?
> 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
> Fix For: 1.5
>
>
> 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)
