[
https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205501#comment-15205501
]
Jiangjie Qin commented on KAFKA-3442:
-------------------------------------
[~dana.powers] Are you expecting a RecordSizeTooLargeException? One change
after KIP-31/32 is that if down-conversion occurred on the broker side, on
consumer side the traditional way of detecting the RecordSizeTooLarge no longer
work.
In your case, if you the message format on broker is 0.10.0 and your
FetchRequest version is < v2, the consumer will not get any bytes back.
However, if you fetch using FetchRequest v2, you will be able to get ~1024
bytes.
> 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
> 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)
