wenfengwang edited a comment on pull request #3289: URL: https://github.com/apache/rocketmq/pull/3289#issuecomment-905582091
> > pulsar or kafka‘s partitionId is gobal[0..N] , whereever topic partition be on which broker， > > using the fields of topic and partitionId, we can find the partition's address; > > but in RocketMQ original routing protocols, the routing info is calculated by client's logic; > > where the topic partition be shift to other broker, In pulsar or Kafka system, > > use compatible protocols, it's difficult to find correct topic address > > The connector component is the preferred solution for data communication between different message products, and the protocol benchmarking should not be modified directly. The RocketMQ as an independent MQ product, it don't and shouldn't provide any efforts on compatibility by other MQ product. I think use High Level API is a good way to achieve this goal, the OpenMessaging spec is a good choice, https://github.com/openmessaging/openmessaging-java, https://github.com/openmessaging/openmessaging-benchmark -- 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]
