[jira] [Updated] (KAFKA-684) ConsoleProducer does not have the queue-size option

[ https://issues.apache.org/jira/browse/KAFKA-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxime Brugidou updated KAFKA-684: -- Fix Version/s: 0.8 Affects Version/s: 0.8 Status: Patch Available (was:

[jira] [Updated] (KAFKA-684) ConsoleProducer does not have the queue-size option

[ https://issues.apache.org/jira/browse/KAFKA-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxime Brugidou updated KAFKA-684: -- Attachment: KAFKA-684.patch ConsoleProducer does not have the queue-size option

[jira] [Updated] (KAFKA-685) ConsoleOffsetChecker does not work with 0.8

[ https://issues.apache.org/jira/browse/KAFKA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxime Brugidou updated KAFKA-685: -- Description: The ConsoleOffsetChecker does not work anymore with 0.8, this tool is very useful

[jira] [Updated] (KAFKA-685) ConsoleOffsetChecker does not work with 0.8

[ https://issues.apache.org/jira/browse/KAFKA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxime Brugidou updated KAFKA-685: -- Description: The ConsoleOffsetChecker does not work anymore with 0.8, this tool is very useful

[jira] [Updated] (KAFKA-685) ConsoleOffsetChecker does not work with 0.8

[ https://issues.apache.org/jira/browse/KAFKA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxime Brugidou updated KAFKA-685: -- Description: The ConsoleOffsetChecker does not work anymore with 0.8, this tool is very useful

[jira] [Updated] (KAFKA-685) ConsoleOffsetChecker does not work with 0.8

[ https://issues.apache.org/jira/browse/KAFKA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxime Brugidou updated KAFKA-685: -- Description: The ConsoleOffsetChecker does not work anymore with 0.8, this tool is very useful

[jira] [Updated] (KAFKA-685) ConsoleOffsetChecker does not work with 0.8

[ https://issues.apache.org/jira/browse/KAFKA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxime Brugidou updated KAFKA-685: -- Description: The ConsoleOffsetChecker does not work anymore with 0.8, this tool is very useful

[jira] [Updated] (KAFKA-685) ConsoleOffsetChecker does not work with 0.8

[ https://issues.apache.org/jira/browse/KAFKA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxime Brugidou updated KAFKA-685: -- Attachment: KAFKA-685.patch ConsoleOffsetChecker does not work with 0.8

Re: git workflow

Diff/patch makes it easy for non-committer to contribute. On 1/7/13 12:52 AM, Derek Chen-Becker wrote: Although I haven't contributed much here yet, I did want to ask: why diff/patch and not pull/merge? I know my work on getting the SBT build working with a modern SBT was quite a headache for

Re: git workflow

It makes it easier for a non-committer to contribute via email, but with publicly available repos (a la GitHub) it's just as easy to merge from a remote (and doesn't require contorting through hoops for certain scenarios). On Jan 7, 2013 7:45 AM, David Arthur mum...@gmail.com wrote: Diff/patch

Re: git workflow

The reason we take diffs is because traditionally the mandatory Apache toolchain is svn+jira+patch/diff. When we were on github of course we used that. I'm actually not sure of the Apache rules here. Can we just directly accept github pull requests? I.e. you fork the apache mirror and send a pull

Re: git workflow

If it's mandated by Apache rules, I understand, but I do think that GitHub/git provide improved workflow over SVN + patch. Apache appears to be mirroring to GitHub anyway: https://github.com/apache/kafka You even have a pull request (5 months old) already. Things like pull request

[jira] Subscription: outstanding kafka patches

Issue Subscription Filter: outstanding kafka patches (56 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-685 ConsoleOffsetChecker does not work with 0.8 https://issues.apache.org/jira/browse/KAFKA-685 KAFKA-684

[jira] [Commented] (KAFKA-684) ConsoleProducer does not have the queue-size option

[ https://issues.apache.org/jira/browse/KAFKA-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13546291#comment-13546291 ] Jun Rao commented on KAFKA-684: --- Thanks for the patch. It looks good. While you are here,

LinkedIn's Kafka-Hadoop ETL pipeline is open source

Hey All, There has been interesting in getting something a little more sophisticated then the Input- and OutputFormat we include in contrib for reading Kafka data into HDFS. Internally at LinkedIn we have had a pretty sophisticated system that we use for Kafka ETL. It automatically discovers

[jira] [Commented] (KAFKA-685) ConsoleOffsetChecker does not work with 0.8

[ https://issues.apache.org/jira/browse/KAFKA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13546397#comment-13546397 ] Jun Rao commented on KAFKA-685: --- Thanks for the patch. The code looks good. Got the

[jira] [Updated] (KAFKA-648) Use uniform convention for naming properties keys

[ https://issues.apache.org/jira/browse/KAFKA-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriram Subramanian updated KAFKA-648: - Attachment: configchanges-v2.patch 1. Standardized usage of enable 2. Fixed config names

[jira] [Created] (KAFKA-686) 0.8 Kafka broker should give a better error message when running against 0.7 zookeeper

Jay Kreps created KAFKA-686: --- Summary: 0.8 Kafka broker should give a better error message when running against 0.7 zookeeper Key: KAFKA-686 URL: https://issues.apache.org/jira/browse/KAFKA-686 Project:

[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven repository

[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13546624#comment-13546624 ] Jun Rao commented on KAFKA-133: --- Joe, do you plan to merge the commit to the 0.8 branch?