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

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 16:10:48 UTC

[GitHub] [beam] kennknowles opened a new issue, #18030: Support other message than TextMessage in JmsIO

kennknowles opened a new issue, #18030:
URL: https://github.com/apache/beam/issues/18030

   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.
   
   Imported from Jira [BEAM-585](https://issues.apache.org/jira/browse/BEAM-585). Original Jira may contain additional context.
   Reported by: jbonofre.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org