[BUG REPORT] Partition order messages are out of order.

[onceicy]

BUG REPORT

1. Please describe the issue you observed:

• What did you do (The steps to reproduce)?

Start a source task such as a RmqSourceTask. Then let the source task send some messages when Calling sourceMessage.getKeys() yields the same return value.

• What is expected to see?

The messages sent to the target RocketMQ cluster via the connector are preserved in the same order as the source messages.

• What did you see instead?

The messages sent to the target RocketMQ cluster via the connector are out of order.

2. Please tell us about your environment:

rocketmq 4.7, RmqSourceTask

3. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

producer.send(sourceMessage, callback) is executed asynchronously, meaning it runs independently from the main execution flow and does not block the calling thread. When sending partition order messages, connector should use synchronous send functions such as producer.send(sourceMessage) instead of asynchronous functions such as producer.send(sourceMessage, callback).