BewareMyPower commented on issue #11962: URL: https://github.com/apache/pulsar/issues/11962#issuecomment-914970028
@wangjialing218 The conversion is unavoidable. We have to sacrifice either producer or consumer side. But before this proposal, if we're going to support both Kafka and Pulsar clients, the conversion was: 1. Pulsar producer -> BK 2. Kafka producer -> convert to Pulsar format -> BK 3. BK -> convert to Kafka format -> Kafka consumer 4. BK -> Pulsar consumer After this proposal: 1. Pulsar producer -> BK 2. Kafka producer -> BK 3. BK -> convert if necessary (by KoP) -> Kafka consumer 4. BK -> convert if necessary (by MessageConverter) -> Pulsar consumer For your second question > If the topic has multi subscriptions, one message could be dispatched to multi consumers, does the covert of this message happen multi times in this case? Currently yes. But I'm not sure if the implementation can be improved. In my demo implementation I performed the conversion in `ServerCnx#newMessageAndIntercept`. But maybe it could be performed immediately after the entries were read. -- 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]
