[jira] [Created] (IGNITE-6855) Refactor JMSStreamer to better align with overall streamer design

2017-11-09 Thread Timothy Steffens (JIRA)
Timothy Steffens created IGNITE-6855: Summary: Refactor JMSStreamer to better align with overall streamer design Key: IGNITE-6855 URL: https://issues.apache.org/jira/browse/IGNITE-6855 Project

Re: JMSStreamer enhancement -- needs to support multiple IgniteDataStreamers.

2017-11-09 Thread Timothy Steffens
while reusing most of JmsStreamer code. Thoughts? -Val On Wed, Nov 8, 2017 at 1:31 PM, Dmitriy Setrakyan wrote: > On Thu, Nov 9, 2017 at 5:06 AM, Timothy Steffens < > timothy.steff...@yahoo.com > > wrote: > > > Can the JMSStreamer be configured to inspect the message prior

Re: JMSStreamer enhancement -- needs to support multiple IgniteDataStreamers.

2017-11-08 Thread Timothy Steffens
separate JMS streamer per cache? In my view, it is more intuitive to keep one-to-one relationship between JMS streamer and the data streamer. D. On Wed, Nov 8, 2017 at 9:40 AM, Timothy Steffens < timothy.steff...@yahoo.com.invalid> wrote: > Dev - > > I have a use case that is not able

JMSStreamer enhancement -- needs to support multiple IgniteDataStreamers.

2017-11-07 Thread Timothy Steffens
Dev - I have a use case that is not able to be addressed with the existing JMSStreamer functionality so I would like to propose an enhancement. The use case is such that I have a series of database tables and am writing messages into a shared JMS queue for each table update. These messages are

JMSStreamer enhancement -- needs to support multiple IgniteDataStreamers.

2017-11-07 Thread Timothy Steffens
Dev - I have a use case that is not able to be addressed with the existing JMSStreamer functionality so I would like to propose an enhancement. The use case is such that I have a series of database tables and am writing messages into a shared JMS queue for each table update. These messages are th