[jira] [Commented] (KAFKA-4621) Fetch Request V3 docs list max_bytes twice
[ https://issues.apache.org/jira/browse/KAFKA-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819844#comment-15819844 ] Jeff Widman commented on KAFKA-4621: Yeah, I saw that... perhaps the descriptions could also be cleaned up slightly to make it more clear what they're referring to... I'll try to put together a PR at some point here... > Fetch Request V3 docs list max_bytes twice > -- > > Key: KAFKA-4621 > URL: https://issues.apache.org/jira/browse/KAFKA-4621 > Project: Kafka > Issue Type: Bug > Components: documentation >Affects Versions: 0.10.2.0 >Reporter: Jeff Widman >Priority: Minor > > http://kafka.apache.org/protocol.html > Fetch Request (Version: 3) lists "max_bytes" twice, but with different > descriptions. This is confusing, as it's not apparent if this is an > accidental mistake or a purposeful inclusion... if purposeful, it's not clear > why. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-4621) Fetch Request V3 docs list max_bytes twice
[ https://issues.apache.org/jira/browse/KAFKA-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819790#comment-15819790 ] Ismael Juma commented on KAFKA-4621: One of them is for the whole request and the other is for the partition. If you look at the definition of the fetch request instead of just the table, it should be clear. Looks like we need to improve the table generation to handle such cases better. > Fetch Request V3 docs list max_bytes twice > -- > > Key: KAFKA-4621 > URL: https://issues.apache.org/jira/browse/KAFKA-4621 > Project: Kafka > Issue Type: Bug > Components: documentation >Affects Versions: 0.10.2.0 >Reporter: Jeff Widman >Priority: Minor > > http://kafka.apache.org/protocol.html > Fetch Request (Version: 3) lists "max_bytes" twice, but with different > descriptions. This is confusing, as it's not apparent if this is an > accidental mistake or a purposeful inclusion... if purposeful, it's not clear > why. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
