Re: [jira] [Commented] (KAFKA-656) Add Quotas to Kafka

This thread might be of some use, it discusses the memory footprint when using metrics: https://groups.google.com/forum/#!topic/metrics-user/T68H70ea1Og On Sat, Jul 13, 2013 at 5:35 PM, Swapnil Ghike (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/KAFKA-656?page=com.atlassian.ji

[jira] [Resolved] (KAFKA-968) Typographical Errors in Output

[ https://issues.apache.org/jira/browse/KAFKA-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rebecca Sealfon resolved KAFKA-968. --- Resolution: Fixed I checked the repository and this seems to have been fixed.

[jira] [Commented] (KAFKA-974) can't use public release maven repo because of failure of downloaded dependency

[ https://issues.apache.org/jira/browse/KAFKA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708177#comment-13708177 ] Joe Stein commented on KAFKA-974: - tried this with no luck, same error diff --git a/projec

[jira] [Commented] (KAFKA-974) can't use public release maven repo because of failure of downloaded dependency

[ https://issues.apache.org/jira/browse/KAFKA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708183#comment-13708183 ] Joe Stein commented on KAFKA-974: - well, as far as SBT goes http://www.scala-sbt.org/relea

[jira] [Updated] (KAFKA-974) can't use public release maven repo because of failure of downloaded dependency

[ https://issues.apache.org/jira/browse/KAFKA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-974: Status: Patch Available (was: Open) > can't use public release maven repo because of failure of downloa

[jira] [Updated] (KAFKA-974) can't use public release maven repo because of failure of downloaded dependency

[ https://issues.apache.org/jira/browse/KAFKA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-974: Attachment: KAFKA-974.v2.patch That last fix did work and attached patch to use public maven "org.apache.k

0.8.0-beta1 is now available in public maven

With SBT you can use 0.8.1-beta built with any of these four Scala versions in libraryDependencies now "org.apache.kafka" % "kafka_2.9.2" % "0.8.0-beta1" intransitive() or "org.apache.kafka" % "kafka_2.9.1" % "0.8.0-beta1" intransitive() or "org.apache.kafka" % "kafka_2.8.2" % "0.8.0-beta1" in

Re: 0.8.0-beta1 is now available in public maven

SBT uses Maven Central as a default repository (local ivy too). The artifacts are published to Maven Central so nothing you should have to-do except to specify the libraryDependencies In regards to 2.10.X support I took a really quick look at https://issues.apache.org/jira/browse/KAFKA-717 (lots

[jira] [Commented] (KAFKA-717) scala 2.10 build support

[ https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708204#comment-13708204 ] Joe Stein commented on KAFKA-717: - looking at the simple patch not sure changing the scalaV

Re: 0.8.0-beta1 is now available in public maven

Thanks for doing this! I'm wondering whether there is a reason to prefer one version of scala over another, if we don't have any other particular scala dependency in our code. Are the newer versions better/more efficient, some how? We've essentially been using 2.8.0 so far, which seems to be fin