The documentation currently includes the caveat that "As an optimization
the server is allowed to return a partial message at the end of the message
set. Clients should handle this case."
As to whether or not this is a good feature: it is definitely a bad
feature. It was originally there because w
Yes that is a bit of a caveat in using zero-copy when sending
FetchResponses. i.e., the broker cannot introspect the message-set and
lop off any trailing piece. I think this is just something that needs
to be documented clearly on that wiki. So there is some overhead for
the client implementation i
