zhangyang
zhangyang
Can you create a corresponding issue for this PR?
Can you create an issue for this PR?
Can you resolve the conflict？
Can you create an ISSUE for this PR?
OffsetMsgId needs to be added to the keys when synchronizing messages. The msg offset in source and target is verified by offsetMsyId.
@lizhiboo Hello, do you think the above implementation is not in line with the original intention of the community design? Can I have a brief conversation with you?
> At first，the origin design is use the target cluster as connector host cluster,In this way, messages can be directly synchronized to another cluster without going through a sink task,...
@duhenglucky @odbozhou For Replicator, I disassembled what I am currently doing and what I have completed, and the list of solutions is as above. In the last meetup, some implementation...
> > @duhenglucky @odbozhou For Replicator, I disassembled what I am currently doing and what I have completed, and the list of solutions is as above. In the last meetup,...
> Up, do we have a dashboard plan? Do we support the bidirectional replicator now? There is currently no dashboard plan. We have also discussed bidirectional replicator internally, but the...