flowchartsman commented on issue #447: URL: https://github.com/apache/pulsar-client-go/issues/447#issuecomment-765654177
Okay, so wait, I’m confused. I guess it might help to discuss the intended purpose of maxmessagesize. If it’s just a knob to adjust cluster performance and storage allocation and such, that’s one thing, but if it is intended as a to guarantee that, for example, a consumer can keep a fixed buffer for handing the payload, then this would seem to be correct behavior, am I right? Are the Java and C++ clients actually *incorrect* in allowing message compression before payload size checking? ---------------------------------------------------------------- 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]
