[
https://issues.apache.org/jira/browse/IGNITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001927#comment-15001927
]
Roman Shtykh commented on IGNITE-529:
-------------------------------------
Anton,
If IgniteDataStreamer can bring more speed, I will use it rather than using
cache.putAll() then. Flume handles large loads of data.
Having something like this in EventTransformer interface
{code}
@Nullable List<IgniteBiTuple<K,V>> transform(Event event);
{code}
instead of
{code}
@Nullable Map<K, V> transform(Event event);
{code}
might reduce memory overhead but slow down transformation a bit. But in the
next PR I will add batching, as it is done in other sink implementations, which
will speed up processing in overall.
As far as I know, having a channel and feeding events should be sufficient to
test the sink. Normally, before submitting code I check it with a simple full
deployment I describe in README.
> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --------------------------------------------------------------
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
> Reporter: Dmitriy Setrakyan
> Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from
> Apache Flume and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
