[
https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207068#comment-15207068
]
Dana Powers commented on KAFKA-3442:
------------------------------------
I think old clients might work better if the single partial message were
replaced with an empty message and a record-too-large error. Most old clients
will simply "hang" and the user has to figure out for themselves that there is
a message that is too big (is this logged by the broker?). Returning an error
code will either be ignored or cause a crash that the user is likely expecting.
This failure to raise an error is, I think, the reason that the java client
added a check for a message set with only partial message so that it can
simulate an error and alert the user.
> FetchResponse size exceeds max.partition.fetch.bytes
> ----------------------------------------------------
>
> Key: KAFKA-3442
> URL: https://issues.apache.org/jira/browse/KAFKA-3442
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.0
> Reporter: Dana Powers
> Assignee: Jiangjie Qin
> Priority: Blocker
> Fix For: 0.10.0.0
>
>
> Produce 10000 byte message to topic foobar
> Fetch foobar w/ max.partition.fetch.bytes=1024
> Test expects to receive a truncated message (~1024 bytes). 0.8 and 0.9 pass
> this test, but 0.10 FetchResponse has full message, exceeding the max
> specified in the FetchRequest.
> I tested with v0 and v1 apis, both fail. Have not tested w/ v2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
