[jira] [Commented] (KAFKA-406) Gzipped payload is a fully wrapped Message (with headers), not just payload

[ https://issues.apache.org/jira/browse/KAFKA-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418163#comment-13418163 ] Lorenzo Alberton commented on KAFKA-406: After sleeping over this, I think it's a r

[jira] [Commented] (KAFKA-376) expose different data to fetch requests from the follower replicas and consumer clients

[ https://issues.apache.org/jira/browse/KAFKA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418310#comment-13418310 ] Prashanth Menon commented on KAFKA-376: --- I actually didn't get a chance to look at th

[jira] [Commented] (KAFKA-376) expose different data to fetch requests from the follower replicas and consumer clients

[ https://issues.apache.org/jira/browse/KAFKA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418337#comment-13418337 ] Jay Kreps commented on KAFKA-376: - Awesome, sounds great! No pressure, just didn't want it

[jira] [Commented] (KAFKA-406) Gzipped payload is a fully wrapped Message (with headers), not just payload

[ https://issues.apache.org/jira/browse/KAFKA-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418376#comment-13418376 ] Jay Kreps commented on KAFKA-406: - I actually don't see how the compression flag can slip t

[jira] [Commented] (KAFKA-406) Gzipped payload is a fully wrapped Message (with headers), not just payload

[ https://issues.apache.org/jira/browse/KAFKA-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418395#comment-13418395 ] Jay Kreps commented on KAFKA-406: - Oh yes, and the other design requirement we had was that

Re: [jira] [Commented] (KAFKA-406) Gzipped payload is a fully wrapped Message (with headers), not just payload

Does it mean that currently if a producer publishes an uncompressed message to the server which has local log format configured to compressed, consumers will receive compressed messages when fetching? On Jul 19, 2012 5:08 PM, "Jay Kreps (JIRA)" wrote: > > [ > https://issues.apache.org/jira/b

Re: [jira] [Commented] (KAFKA-406) Gzipped payload is a fully wrapped Message (with headers), not just payload

Currently we always retain the data in the format that it was produced. It would be a fairly small change, though, to allow a server-override parameter that would have the server either always compress the data or always decompress it before writing it to the log. -Jay On Thu, Jul 19, 2012 at 10:

Re: [jira] [Commented] (KAFKA-406) Gzipped payload is a fully wrapped Message (with headers), not just payload

Well then I'm not sure if I follow the re-compression line of reasoning behind the double wrapping.. but I'm only starting to look into details of Kafka so maybe there's another layer of compression that lumps messages together for saving i/o between log or within cluster.. anyways as for the doubl

[jira] Subscription: outstanding kafka patches

Issue Subscription Filter: outstanding kafka patches (41 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-405 Improve the high water mark maintenance to store high watermarks for all partitions in a single file on disk ht

[jira] [Commented] (KAFKA-371) Creating topic of empty string puts broker in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418586#comment-13418586 ] Neha Narkhede commented on KAFKA-371: - +1. Minor comment - Change logCleanupThreshol

[jira] [Updated] (KAFKA-352) Throw exception to client if it makes a produce/consume request to a Kafka broker for a topic that hasn't been created

[ https://issues.apache.org/jira/browse/KAFKA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-352: Resolution: Fixed Fix Version/s: 0.8 Status: Resolved (was: Patch Available) Than

[jira] [Commented] (KAFKA-371) Creating topic of empty string puts broker in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418632#comment-13418632 ] Jonathan Creasy commented on KAFKA-371: --- Does it make sense to have a function to "va

[jira] [Comment Edited] (KAFKA-371) Creating topic of empty string puts broker in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418632#comment-13418632 ] Jonathan Creasy edited comment on KAFKA-371 at 7/19/12 8:20 PM: -

Re: Build failed in Jenkins: Kafka-0.8 #7

Does anyone know what this scaladoc failure is? It is totally impossible to understand that error -Jay On Thu, Jul 19, 2012 at 3:04 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [jkreps] KAFKA-371 Refa

[jira] [Commented] (KAFKA-371) Creating topic of empty string puts broker in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418736#comment-13418736 ] Jay Kreps commented on KAFKA-371: - Got it, committed. > Creating topic of

[jira] [Commented] (KAFKA-371) Creating topic of empty string puts broker in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418745#comment-13418745 ] Jay Kreps commented on KAFKA-371: - Hey Jonathan, I don't think so, but I may have misunders

[jira] [Updated] (KAFKA-405) Improve the high water mark maintenance to store high watermarks for all partitions in a single file on disk

[ https://issues.apache.org/jira/browse/KAFKA-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-405: Attachment: kafka-405-v2.patch 1. Good point. Changed the name to Log.truncateTo(targetOffset) 2. It