Re: Protocol documentation draft

Is the 0.8 protocol pretty much frozen at this point? If so, I'd like to start updating my python client. Also, I'm guessing 0.8 will be backwards compatible with 0.7 (due to the API versioning) -David On Nov 29, 2012, at 7:47 PM, Jay Kreps wrote: > Okay here is a proposal to address the issu

Re: Protocol documentation draft

Not quite. I noticed a few bugs that I pointed out in the previous email. I would like to correct these today before we officially freeze it. So maybe give me through Monday? At that point it would be absolutely fantastic to have someone try to work off the document rather than off our code, and im

[jira] [Commented] (KAFKA-640) System Test Failures : kafka.common.InvalidClientIdException in broker log4j messages

[ https://issues.apache.org/jira/browse/KAFKA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507483#comment-13507483 ] Neha Narkhede commented on KAFKA-640: - +1, LGTM > System Test Failures

[jira] [Commented] (KAFKA-608) getTopicMetadata does not respect producer config settings

[ https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507494#comment-13507494 ] Jun Rao commented on KAFKA-608: --- Thanks for the patch. Looks good overall. Some comments: 1.

[jira] [Resolved] (KAFKA-640) System Test Failures : kafka.common.InvalidClientIdException in broker log4j messages

[ https://issues.apache.org/jira/browse/KAFKA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-640. - Resolution: Fixed Assignee: Swapnil Ghike Thanks for the patch, just committed it.

[jira] [Closed] (KAFKA-640) System Test Failures : kafka.common.InvalidClientIdException in broker log4j messages

[ https://issues.apache.org/jira/browse/KAFKA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-640. --- > System Test Failures : kafka.common.InvalidClientIdException in broker log4j > messages > -

[jira] [Updated] (KAFKA-608) getTopicMetadata does not respect producer config settings

[ https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-608: Attachment: kafka-608-v2.patch 1. My bad, included in this patch 2. Absolutely, prepended "Message:

[jira] [Commented] (KAFKA-608) getTopicMetadata does not respect producer config settings

[ https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507546#comment-13507546 ] Swapnil Ghike commented on KAFKA-608: - Is including broker.list in properties necessary

[jira] [Commented] (KAFKA-608) getTopicMetadata does not respect producer config settings

[ https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507552#comment-13507552 ] Neha Narkhede commented on KAFKA-608: - yes, you can't instantiate a ProducerConfig obje

[jira] [Updated] (KAFKA-637) Separate log4j environment variable from KAFKA_OPTS in kafka-run-class.sh

[ https://issues.apache.org/jira/browse/KAFKA-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur updated KAFKA-637: --- Status: Patch Available (was: Open) > Separate log4j environment variable from KAFKA_OPTS in kafk

[jira] [Updated] (KAFKA-642) Protocol tweaks for 0.8

[ https://issues.apache.org/jira/browse/KAFKA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-642: Attachment: KAFKA-642-v1.patch This patch implements the changes described above with the following exceptio

Re: new mailing lists

Looks like the previous one got closed due to a Apache process issue. Filed another one identical to Giraph's - https://issues.apache.org/jira/browse/INFRA-5583 Thanks, Neha On Wed, Nov 28, 2012 at 5:19 PM, Neha Narkhede wrote: > Thanks for the note, Owen ! Filed a ticket for Kafka's website - >

[jira] [Commented] (KAFKA-642) Protocol tweaks for 0.8

[ https://issues.apache.org/jira/browse/KAFKA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507773#comment-13507773 ] Jay Kreps commented on KAFKA-642: - Appears to pass basic system tests. > P

[jira] [Commented] (KAFKA-642) Protocol tweaks for 0.8

[ https://issues.apache.org/jira/browse/KAFKA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507807#comment-13507807 ] Neha Narkhede commented on KAFKA-642: - I guess we want to include this on the 0.8 branc

[jira] [Commented] (KAFKA-608) getTopicMetadata does not respect producer config settings

[ https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507821#comment-13507821 ] Jun Rao commented on KAFKA-608: --- +1. For #2, may be we should prepend a bit more text like "S

[jira] [Commented] (KAFKA-642) Protocol tweaks for 0.8

[ https://issues.apache.org/jira/browse/KAFKA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507846#comment-13507846 ] Neha Narkhede commented on KAFKA-642: - Thanks for the patch, reviewed the one that appl

[jira] [Created] (KAFKA-643) Refactor api definition layer

Jay Kreps created KAFKA-643: --- Summary: Refactor api definition layer Key: KAFKA-643 URL: https://issues.apache.org/jira/browse/KAFKA-643 Project: Kafka Issue Type: Improvement Affects Versions:

[jira] [Updated] (KAFKA-598) decouple fetch size from max message size

[ https://issues.apache.org/jira/browse/KAFKA-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-598: - Attachment: KAFKA-598-v1.patch I spent the better part of a day rebasing - serves me right for letting thi