Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: kafka-dev@incubator.apache.org
Date: Mon, 12 Mar 2012 22:04:47 +0000 (UTC)
From: "AaronR (Updated) (JIRA)" <jira@apache.org>
To: kafka-dev@incubator.apache.org
Message-ID: 
 <1882102165.5044.1331589887532.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1921453397.40891.1331245678647.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (KAFKA-298) Go Client support max message size
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/KAFKA-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

AaronR updated KAFKA-298:
-------------------------

    Attachment: kafka298-v2.diff

updating based on changes to 297, 296
                
> Go Client support max message size
> ----------------------------------
>
>                 Key: KAFKA-298
>                 URL: https://issues.apache.org/jira/browse/KAFKA-298
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 0.7.1
>            Reporter: AaronR
>         Attachments: NOTICE, kafka298-v2.diff, messageedge.patch
>
>
> The go client has a bug when max message size is reached on broker-consumer request, such that resulting bytes sent to consumer contain a truncated/partial message as last message.   Go client was not recognizing and handling this partial message.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira