odbozhou commented on PR #463: URL: https://github.com/apache/rocketmq-connect/pull/463#issuecomment-1500014066
> dest.endpoint dest.endpoint > The connector is depolyed alone , so we should not bind to only one rocketmq cluster. We can use the connector as a channel, user can config the source and dest. > > And then what's the meaning to config `dest.endpoint` in `rocketmq-replicator` ? @odbozhou The purpose of dest.endpoint is to allow the replicator to connect itself to the current cluster, so that the ability to automatically create a target topic or automatically create a consumerGroup can be realized. For example, the replicator_checkpoint topic needs to be created in the checkpoint connector to the target rocketmq cluster. In addition to the points mentioned above, it is also very important that the consumer side can use its perfect offset management mechanism to easily achieve at least one transmission. Because the producer logic is relatively simple, it can achieve at least one transmission in scenarios with poor network conditions. A transfer is more difficult. This is why replicator uses source to implement instead of sink. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
