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/09/26 14:56:20 UTC

[jira] [Created] (BEAM-675) Introduce message mapper in JmsIO

Jean-Baptiste Onofré created BEAM-675:
-----------------------------------------

             Summary: Introduce message mapper in JmsIO
                 Key: BEAM-675
                 URL: https://issues.apache.org/jira/browse/BEAM-675
             Project: Beam
          Issue Type: Improvement
          Components: sdk-java-extensions
            Reporter: Jean-Baptiste Onofré
            Assignee: Jean-Baptiste Onofré


Currently, the {{JmsIO}} deals with a {{JmsRecord}} and populates the reader populates the {{PCollection}} with it.

It also deals "only" with {{TextMessage}}.

It would be helpful to allow users to provide {{MessageMapper}} function allowing to "convert" the JMS Message as a custom POJO, and eventually deal with other type of JMS Message ({{BytesMessage}}, {{MapMessage}}, ...).

By default, the IO will still use {{JmsRecord}}.



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