bigbang489 edited a comment on issue #7752: URL: https://github.com/apache/pulsar/issues/7752#issuecomment-670458320
We are building an adapter to integrate Pulsar to SAP Integraion system. Sender adapter will consume message from a topic, Receiver adapter will produce message to a topic. For Receiver adapter, there is no certain time when it is called, if it's called once a month and keeping connection open for a long time to just send a message a month is not a good idea. That is why we decided to close and re-connect to broker everytime. Btw, Is there any way to tell the Pulsar client (that has producers only) that it should close the connectivity if there is no message to publish after an amount of time, and re-connect to brokers when it needs to send a message again? For the > If we only send the schema version, there is no way for us to verify if the client is using the right schema. Because a client can just provide a random schema number and produce the data with a different schema. There is no guarantee that the encoded data sent to brokers is using correct schema in case they using their own custom Schema implementation. I think skipping verifying SchemaInfo will make sense, if the client itself can assures the correctness of schema version. By doing this, not only faster connectivity establishment, but also be able to send messages with diffrent versions without creating new producers for each version. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
