Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D20A31885F for ; Sat, 8 Aug 2015 23:39:47 +0000 (UTC) Received: (qmail 97079 invoked by uid 500); 8 Aug 2015 23:39:47 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 97055 invoked by uid 500); 8 Aug 2015 23:39:47 -0000 Mailing-List: contact issues-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.incubator.apache.org Delivered-To: mailing list issues@ignite.incubator.apache.org Received: (qmail 97045 invoked by uid 99); 8 Aug 2015 23:39:47 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Aug 2015 23:39:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5E3CF19F53F for ; Sat, 8 Aug 2015 23:39:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.77 X-Spam-Level: * X-Spam-Status: No, score=1.77 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id zDfhA5nFs6pV for ; Sat, 8 Aug 2015 23:39:46 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 63F5B2100B for ; Sat, 8 Aug 2015 23:39:46 +0000 (UTC) Received: (qmail 97005 invoked by uid 99); 8 Aug 2015 23:39:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Aug 2015 23:39:46 +0000 Date: Sat, 8 Aug 2015 23:39:45 +0000 (UTC) From: =?utf-8?Q?Ra=C3=BAl_Kripalani_=28JIRA=29?= To: issues@ignite.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-534) Implement IgniteJmsStreamer to stream data from a JMS broker like ActiveMQ MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-534?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1466= 3204#comment-14663204 ]=20 Ra=C3=BAl Kripalani commented on IGNITE-534: --------------------------------------- Oh, I just came across this: https://cwiki.apache.org/confluence/display/IG= NITE/Streamers+Implementation+Guidelines. So I will have to refactor my imp= lementation a little bit, but in general it fits the model pretty well (e.g= . I created a custom {{MessageTransformer}} class instead of using {{Stream= TupleExtractor}}). However, the base {{StreamTupleExtractor}} has a shortcoming: it is only ca= pable of generate a single cache entry out of an incoming stream message. I= will have to extend {{StreamTupleExtractor}}. > Implement IgniteJmsStreamer to stream data from a JMS broker like ActiveM= Q > -------------------------------------------------------------------------= - > > 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=C3=BAl Kripalani > > We have {{IgniteDataStreamer}} which is used to load data into Ignite und= er high load. It was previously named {{IgniteDataLoader}}, see ticket IGNI= TE-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 implementa= tion-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 conver= ter. 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)