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

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/09/02 17:08:41 UTC

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

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

Beam JIRA Bot commented on BEAM-585:
------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.

> 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: io-java-jms
>            Reporter: Jean-Baptiste Onofré
>            Priority: P3
>
> 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
(v8.3.4#803005)