[
https://issues.apache.org/jira/browse/IGNITE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996318#comment-14996318
]
Anton Vinogradov commented on IGNITE-529:
-----------------------------------------
Roman,
1) I meant that streamer should use already created cache specified at it's
configuration. In other words, user should create cache and pass it at a
streamer parameter.
Try code simmilar to following:
try (IgniteDataStreamer<Long, String> dataStreamer =
grid().dataStreamer(null)) {
Streamer streamer = new StreamerInstance(dataStreamer);
2) JmsStreamer seems to be wrongly designed. Please follow
https://cwiki.apache.org/confluence/display/IGNITE/Streamers+Implementation+Guidelines
.
Using StreamAdapter.addMessage() is a correct way. Only one of *TupleExtractor
should be used in this case.
> 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)
