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 to picking > it off of the queue? If so, then I can use multiple JMSStreamers as you > suggest. If not, then I cannot since each JMSStreamer will not know if the > next message is for them or for another to process. I do not want to have > multiple queues (one queue per table - which would equate to one > JMSStreamer per queue) due to ongoing maintenance concerns. > To be honest, queue-per-table seems like the most appropriate solution here. I do not think inspecting messages before they get picked off the queue will perform well. If queue-per-table is not possible, then my suggestion would be not to use JMS Streamer at all, and implement your own logic for reading JMS messages and passing them off to the appropriate data streamer. D.
