Matteo Merli
Matteo Merli
@odaira Can you take a look at this? It's on the same line as what described in #106
@odaira Any chance on this one? :)
> Can these binaries in gz format to be uploaded to GH release as part of the client lib release package? Not directly, the releases need to be done to...
That's right, the Java and C++ clients are more permissive in that the message go through if it's below the limit after compression. We should also do the same thing...
Yes, if the max limit is 5MB, it will only guaranteed to accept up to 5MB. Above that, it's just "best effort" to get that to fit in with compression.
One option is to do what we used to do in Python wrapper (before https://github.com/apache/pulsar/pull/5706 was applied). Use a 100millis timeout on the receive to check for interrupted status. That...
In the `MessageRouter`, you're getting a `TopicMetadata` object which will tell you the number of partitions: https://github.com/apache/pulsar-client-go/blob/f17deac7ac47919aa9e46d11d33638672a24d126/pulsar/producer.go#L57 Wouldn't this already solve the problem?
> IIUC, the TopicMetadata gives us the number of partitions at the time the MessageRouter is invoked. For our use case, we need to keep recording the number of partitions...
The cumulative ack was left out on purpose and the reasoning was (in weighted order): * Keep things simple in API * Keep things simple in client impl * Cumulative...