You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2016/10/06 12:22:20 UTC

[jira] [Updated] (BEAM-585) Support other message than TextMessage in JmsIO

     [ https://issues.apache.org/jira/browse/BEAM-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated BEAM-585:
--------------------------------------
    Summary: Support other message than TextMessage in JmsIO  (was: Support other message than TextMessage in JmsIO and improve custom coder support)

> Support other message than TextMessage in JmsIO
> -----------------------------------------------
>
>                 Key: BEAM-585
>                 URL: https://issues.apache.org/jira/browse/BEAM-585
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-extensions
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> Now, the JmsIO only supports TextMessage coming from the broker. JMS broker can provide other kind of messages like BytesMessage, MapMessage, StreamMessage, ObjectMessage. The JmsIO should be able to deal with such kind of messages (implicitly and explicitly). Depending of the JMS message type, the JMS IO should use different coders.
> On the other hand, the JmsIO should allow users to deal with their own custom coders.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)