apache / apache/rocketmq-externals
[rocketmq-replicator] Replicator should support RocketMQConverter
- Dominant language
- Java
- Stars
- 4.6k
- Forks
- 3k
- Avg merge
- 2h 33m
- Merged PRs (30d)
- 1
Description
The issue tracker is **ONLY** used for bug report and feature request.
Any question or RocketMQ proposal please use our [mailing lists](http://rocketmq.apache.org/about/contact/).
**FEATURE REQUEST**
1. Please describe the feature you are requesting.
When using RocketMQConverter, if you accept multiple messages (RmqSourceTask#pollCommonMessage), the replicator directly converts multiple messages into json(JSONObject.toJSONString(msgs)), which is not friendly to directly consume consumer messages.
2. Provide any additional detail on your proposed use case for this feature.
2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
- [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here,
- [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
- ...
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading RmqSourceTask#pollCommonMessage and the RocketMQConverter path, then inspect how JSONObject.toJSONString(msgs) is consumed. Compare the current multi-message output with the expected consumer-facing format. Done means RocketMQConverter supports the requested multi-message case without producing an output that is difficult for consumers to consume directly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100