Codecov Report

Merging #4301 (d55714f) into master (5b8616b) will decrease coverage by 0.52%.
Report is 10 commits behind head on master.
The diff coverage is 46.79%.

❗ Current head d55714f differs from pull request most recent head 8d18898. Consider uploading reports for the commit 8d18898 to get more accurate results

@@             Coverage Diff              @@
##             master    #4301      +/-   ##
============================================
- Coverage     16.87%   16.35%   -0.52%     
+ Complexity     1428     1359      -69     
============================================
  Files           593      594       +1     
  Lines         26035    25419     -616     
  Branches       2366     2394      +28     
============================================
- Hits           4394     4158     -236     
+ Misses        21215    20838     -377     
+ Partials        426      423       -3     

... and 8 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

1. I tried testing your eventmesh-connector-redis module including CloudEventCodec locally, but unfortunately, I didn't see any results. The only configuration change I made was to modify the topic in source-config.yml to TopicTest2. Could you please provide me with the correct verification steps so that I can re-validate? Thank you.

It is all fixed now. (only CloudEvent message support yet)

• Source flow: msg(CloudEvent) -> SourceTopic(Redis Topic) -> SourceWorker -> TopicTest(EventMesh Topic)
• Sink flow: TopicTest(EventMesh Topic) -> SinkWorker -> SinkTopic(Redis Topic) -> msg(CloudEvent)

To Verify SinkWorker

1. Use the TCP cliet demo: https://github.com/apache/eventmesh/blob/master/eventmesh-examples/src/main/java/org/apache/eventmesh/tcp/demo/pub/cloudevents/AsyncPublish.java.
2. make sinkEnable: true in server-config.yml and subject: TEST-TOPIC-TCP-ASYNC in sink-config.yml.
   (TEST-TOPIC-TCP-ASYNC is the top you send to with the TCP cliet demo).
3. start up your eventmesh-runtime and eventmesh-connector-redis
4. You can subscribe to the topic SinkTopic in redis first with your favourite cliet.
5. Sent a cloudevent message with client mentioned in step 1 and you will see it in your redis client.

To Verify SourceWorker

1. make sourceEnable: true in server-config.yml.
2. start up your eventmesh-runtime and eventmesh-connector-redis.
3. Send a cloudevent messang to the topic SourceTopic in redis. Then it will be send to eventmesh, you can check it by logs or in eventmesh-dashboard

2. I'm a bit confused. In your code, you write the type for Redis as ConnectRecord, but CloudEventCodec is used for encoding and decoding the CloudEvent type. Could you clarify my confusion?
3. If CloudEventCodec has no problem, I suggest that you write the comment Duplicate with org.apache.eventmesh.....CloudEventCodec in the code of your module instead of eventmesh-storage-redis module, considering that you copied the code from that module to yours.

• Now the message is write to redis in the CloudEvent type with CloudEventCodec.
• The comment is moved into eventmesh-connector-redis in java doc