Support other message than TextMessage in JmsIO
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
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.
Contributor guide
Research direction
Start by locating the JmsIO entry point and reading how it currently handles TextMessage. Use the JMS message types listed in the issue and the original BEAM-585 context to determine the implicit and explicit coder expectations. Done means JmsIO can handle BytesMessage, MapMessage, StreamMessage, and ObjectMessage, while allowing custom coders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100