ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raúl Kripalani (JIRA) <j...@apache.org>
Subject [jira] [Commented] (IGNITE-534) Implement IgniteJmsStreamer to stream data from a JMS broker like ActiveMQ
Date Sun, 09 Aug 2015 10:02:45 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679072#comment-14679072
] 

Raúl Kripalani commented on IGNITE-534:
---------------------------------------

Oh, I just came across this: https://cwiki.apache.org/confluence/display/IGNITE/Streamers+Implementation+Guidelines.
Unfortunately the base {{StreamTupleExtractor}} is only capable of generating a single cache
entry out of an incoming stream message. This provides little flexibility and the Ignite API
should provide an extractor that returns a {{Map}} (a message can lead to multiple cache entries).
For that reason, I'm sending in my PR with a custom {{MessageTransformer}}, which can be replaced
with a future {{Extractor}} that's capable of returning a {{Map}}.

> Implement IgniteJmsStreamer to stream data from a JMS broker like ActiveMQ
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-534
>                 URL: https://issues.apache.org/jira/browse/IGNITE-534
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: streaming
>            Reporter: Dmitriy Setrakyan
>            Assignee: Raúl Kripalani
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under high load.
It was previously named {{IgniteDataLoader}}, see ticket IGNITE-394.
> We should create {{IgniteJmsStreamer}} which will consume messages from a given queue
or topic of a JMS broker and stream them into Ignite caches.
> Even though we'll use AMQ for testing, this streamer should be implementation-agnostic
and only use JMS constructs where possible.
> See [Apache ActiveMQ|http://activemq.apache.org/] for more information.
> More details to follow, but to the least we should be able to:
> * Convert a JMS message to Ignite data using an optional pluggable converter. If not
provided, we should have some default mechanism.
> * 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)

Mime
View raw message