[jira] [Updated] (KAFKA-717) scala 2.10 build support
[ https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Christiansen updated KAFKA-717: Attachment: 0001-KAFKA-717-Convert-to-scala-2.10.patch Here is an updated patch built from latest HEAD on the 0.8 branch. I also bumbed it to scala 2.10.1 which has some minor bug fixes over 2.10.0. All unit tests pass locally and I did a basic test using the Console producer /consumer. The patch that Darren provided I have tested more extensively but no longer applied to HEAD. > scala 2.10 build support > > > Key: KAFKA-717 > URL: https://issues.apache.org/jira/browse/KAFKA-717 > Project: Kafka > Issue Type: Improvement > Components: packaging >Affects Versions: 0.8 >Reporter: Viktor Taranenko > Labels: build > Attachments: 0001-KAFKA-717-Convert-to-scala-2.10.patch, > kafka_scala_2.10.tar.gz > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KAFKA-852) Remove clientId from OffsetFetchResponse and OffsetCommitResponse
David Arthur created KAFKA-852: -- Summary: Remove clientId from OffsetFetchResponse and OffsetCommitResponse Key: KAFKA-852 URL: https://issues.apache.org/jira/browse/KAFKA-852 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8.1 Reporter: David Arthur Assignee: David Arthur Priority: Minor Fix For: 0.8.1 These are not needed and conflict with the API documentation. Should be removed to be consistent with other APIs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KAFKA-853) Allow OffsetFetchRequest to initialize offsets
David Arthur created KAFKA-853: -- Summary: Allow OffsetFetchRequest to initialize offsets Key: KAFKA-853 URL: https://issues.apache.org/jira/browse/KAFKA-853 Project: Kafka Issue Type: Improvement Components: core Affects Versions: 0.8.1 Reporter: David Arthur Fix For: 0.8.1 It would be nice for the OffsetFetchRequest API to have the option to initialize offsets instead of returning unknown_topic_or_partition. It could mimic the Offsets API by adding the "time" field and then follow the same code path on the server as the Offset API. In this case, the response would need to a boolean to indicate if the returned offset was initialized or fetched from ZK. This would simplify the client logic when dealing with new topics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-850) add an option to show under replicated partitions in list topic command
[ https://issues.apache.org/jira/browse/KAFKA-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623763#comment-13623763 ] Neha Narkhede commented on KAFKA-850: - I meant to review this earlier but got busy fixing KAFKA-849 and KAFKA-851. Looks like this patch needs to be rebased due to the changes in those patches. Please can you rebase ? > add an option to show under replicated partitions in list topic command > --- > > Key: KAFKA-850 > URL: https://issues.apache.org/jira/browse/KAFKA-850 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 0.8 >Reporter: Jun Rao >Assignee: Jun Rao >Priority: Blocker > Attachments: kafka-850.patch > > > For debugging purpose, it's very important to be able to find out the under > replicated partitions quickly. List topic command is a good place to add this > feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KAFKA-854) Upgrade dependencies for 0.8
Scott Carey created KAFKA-854: - Summary: Upgrade dependencies for 0.8 Key: KAFKA-854 URL: https://issues.apache.org/jira/browse/KAFKA-854 Project: Kafka Issue Type: Improvement Affects Versions: 0.8 Reporter: Scott Carey Many of the dependencies that Kafka 0.8 uses are old. It would be a good idea to upgrade all of these where possible. log4j is set to 1.2.15, but the latest is 1.2.17 zookeeper is at 3.3.4, , there is 3.3.6 (August 2012), and 3.4.5 (Nov 2012. 3.4.x includes several major enhancements and fixes over the 3.3.x line. org.slf4j is at 1.6.4, there is 1.6.6 (June 2012) and 1.7.5 (March 2013) net.sf.jopt-simple is at 3.2, there is 3.3 (May 2011) and 4.4 (Jan 2013) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-852) Remove clientId from OffsetFetchResponse and OffsetCommitResponse
[ https://issues.apache.org/jira/browse/KAFKA-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur updated KAFKA-852: --- Attachment: 0001-KAFKA-852-remove-clientId-from-Offset-Fetch-Commit-R.patch > Remove clientId from OffsetFetchResponse and OffsetCommitResponse > - > > Key: KAFKA-852 > URL: https://issues.apache.org/jira/browse/KAFKA-852 > Project: Kafka > Issue Type: Bug > Components: core >Affects Versions: 0.8.1 >Reporter: David Arthur >Assignee: David Arthur >Priority: Minor > Fix For: 0.8.1 > > Attachments: > 0001-KAFKA-852-remove-clientId-from-Offset-Fetch-Commit-R.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > These are not needed and conflict with the API documentation. Should be > removed to be consistent with other APIs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-852) Remove clientId from OffsetFetchResponse and OffsetCommitResponse
[ https://issues.apache.org/jira/browse/KAFKA-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur updated KAFKA-852: --- Status: Patch Available (was: Open) v1 of patch attached, simple change > Remove clientId from OffsetFetchResponse and OffsetCommitResponse > - > > Key: KAFKA-852 > URL: https://issues.apache.org/jira/browse/KAFKA-852 > Project: Kafka > Issue Type: Bug > Components: core >Affects Versions: 0.8.1 >Reporter: David Arthur >Assignee: David Arthur >Priority: Minor > Fix For: 0.8.1 > > Attachments: > 0001-KAFKA-852-remove-clientId-from-Offset-Fetch-Commit-R.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > These are not needed and conflict with the API documentation. Should be > removed to be consistent with other APIs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-850) add an option to show under replicated partitions in list topic command
[ https://issues.apache.org/jira/browse/KAFKA-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-850: -- Attachment: kafka-850_v2.patch Attach patch v2 after rebase. > add an option to show under replicated partitions in list topic command > --- > > Key: KAFKA-850 > URL: https://issues.apache.org/jira/browse/KAFKA-850 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 0.8 >Reporter: Jun Rao >Assignee: Jun Rao >Priority: Blocker > Attachments: kafka-850.patch, kafka-850_v2.patch > > > For debugging purpose, it's very important to be able to find out the under > replicated partitions quickly. List topic command is a good place to add this > feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-850) add an option to show under replicated partitions in list topic command
[ https://issues.apache.org/jira/browse/KAFKA-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-850: -- Status: Patch Available (was: Open) > add an option to show under replicated partitions in list topic command > --- > > Key: KAFKA-850 > URL: https://issues.apache.org/jira/browse/KAFKA-850 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 0.8 >Reporter: Jun Rao >Assignee: Jun Rao >Priority: Blocker > Attachments: kafka-850.patch, kafka-850_v2.patch > > > For debugging purpose, it's very important to be able to find out the under > replicated partitions quickly. List topic command is a good place to add this > feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-854) Upgrade dependencies for 0.8
[ https://issues.apache.org/jira/browse/KAFKA-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Christiansen updated KAFKA-854: Status: Patch Available (was: Open) Here is a patch that revs to the latest for all but ZK. Moving to ZK 3.4.x will require quiet a few test changes so should probably be its own ticket. > Upgrade dependencies for 0.8 > > > Key: KAFKA-854 > URL: https://issues.apache.org/jira/browse/KAFKA-854 > Project: Kafka > Issue Type: Improvement >Affects Versions: 0.8 >Reporter: Scott Carey > Attachments: 0001-KAFKA-854-Upgrade-Deps-to-latest.patch > > > Many of the dependencies that Kafka 0.8 uses are old. It would be a good > idea to upgrade all of these where possible. > log4j is set to 1.2.15, but the latest is 1.2.17 > zookeeper is at 3.3.4, , there is 3.3.6 (August 2012), and 3.4.5 (Nov 2012. > 3.4.x includes several major enhancements and fixes over the 3.3.x line. > org.slf4j is at 1.6.4, there is 1.6.6 (June 2012) and 1.7.5 (March 2013) > net.sf.jopt-simple is at 3.2, there is 3.3 (May 2011) and 4.4 (Jan 2013) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-854) Upgrade dependencies for 0.8
[ https://issues.apache.org/jira/browse/KAFKA-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Christiansen updated KAFKA-854: Attachment: 0001-KAFKA-854-Upgrade-Deps-to-latest.patch > Upgrade dependencies for 0.8 > > > Key: KAFKA-854 > URL: https://issues.apache.org/jira/browse/KAFKA-854 > Project: Kafka > Issue Type: Improvement >Affects Versions: 0.8 >Reporter: Scott Carey > Attachments: 0001-KAFKA-854-Upgrade-Deps-to-latest.patch > > > Many of the dependencies that Kafka 0.8 uses are old. It would be a good > idea to upgrade all of these where possible. > log4j is set to 1.2.15, but the latest is 1.2.17 > zookeeper is at 3.3.4, , there is 3.3.6 (August 2012), and 3.4.5 (Nov 2012. > 3.4.x includes several major enhancements and fixes over the 3.3.x line. > org.slf4j is at 1.6.4, there is 1.6.6 (June 2012) and 1.7.5 (March 2013) > net.sf.jopt-simple is at 3.2, there is 3.3 (May 2011) and 4.4 (Jan 2013) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Kafka and Scala versions
Kafka 0.8 and trunk by default have SBT set up to cross-compile 2.8.0, 2.8.2, 2.9.1 and 2.9.2, and it defaults to 2.8.0. I assume that one of the major contributors requires 2.8.0. Any approximation on how long will that last? Dropping 2.8.0 would be beneficial because some uses of Java Conversions is replaced with Java Converters (in 2.10 +), and Java Converters was not added until 2.8.1. http://stackoverflow.com/questions/8301947/what-is-the-difference-between-j avaconverters-and-javaconversions-in-scala https://issues.apache.org/jira/browse/KAFKA-717 is attempting to add build support for Scala 2.10. The required changes to support 2.10 use Java Converters, which is not available in 2.8.0. The other item required to support Scala 2.10 is to move from scala.StaticAnnotation to scala.annotation.StaticAnnotation. Scala 2.10.x has only scala.annotation.StaticAnnotation. Scala 2.9.x has both scala.StaticAnnotation (deprecated) and scala.annotation.StaticAnnotation. Scala 2.8.x has only scala.StaticAnnotation Dropping support for 2.8.x entirely and supporting only 2.9.x and 2.10.x would make 2.10.x support easy. If 2.8.2 is required (but not 2.8.0), then some sort of conditional compile or two flavors of the source code where scala.annotation.StaticAnnotation is used will be required. Use of StaticAnnotation is very limited. If 2.8.0 must be kept, then two versions of all code that uses Java Conversions APIs will also need to be maintained. I can't find any discussions about 2.8.0 usage requirements. I also don't know enough about sbt to configure cross compilation to use different source files for different cases, which would solve the problems above but add some maintenance burden.
[jira] [Commented] (KAFKA-854) Upgrade dependencies for 0.8
[
https://issues.apache.org/jira/browse/KAFKA-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624145#comment-13624145
]
Dragos Manolescu commented on KAFKA-854:
While you're at it you could also upgrade Jackson. Currently the build file
references org.codehaus.jackson which is old. The upgrade may require some code
changes (the API differs in a few places), all trivial through.
Here's what I use for Scala 2.9.2, they need to be adjusted for 2.8.
libraryDependencies ++= Seq("com.fasterxml.jackson.core" % "jackson-core" %
"2.1.4"
, "com.fasterxml.jackson.core" % "jackson-databind" % "2.1.4"
, "com.fasterxml.jackson.module" % "jackson-module-scala_2.9.2" %
"2.1.3"
)
> Upgrade dependencies for 0.8
>
>
> Key: KAFKA-854
> URL: https://issues.apache.org/jira/browse/KAFKA-854
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Scott Carey
> Attachments: 0001-KAFKA-854-Upgrade-Deps-to-latest.patch
>
>
> Many of the dependencies that Kafka 0.8 uses are old. It would be a good
> idea to upgrade all of these where possible.
> log4j is set to 1.2.15, but the latest is 1.2.17
> zookeeper is at 3.3.4, , there is 3.3.6 (August 2012), and 3.4.5 (Nov 2012.
> 3.4.x includes several major enhancements and fixes over the 3.3.x line.
> org.slf4j is at 1.6.4, there is 1.6.6 (June 2012) and 1.7.5 (March 2013)
> net.sf.jopt-simple is at 3.2, there is 3.3 (May 2011) and 4.4 (Jan 2013)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-826) Make Kafka 0.8 depend on metrics 2.2.0 instead of 3.x
[ https://issues.apache.org/jira/browse/KAFKA-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624150#comment-13624150 ] Dragos Manolescu commented on KAFKA-826: I'm just starting to work on it, will try to finish it over the weekend. > Make Kafka 0.8 depend on metrics 2.2.0 instead of 3.x > - > > Key: KAFKA-826 > URL: https://issues.apache.org/jira/browse/KAFKA-826 > Project: Kafka > Issue Type: Bug > Components: core >Affects Versions: 0.8 >Reporter: Neha Narkhede >Assignee: Dragos Manolescu >Priority: Blocker > Labels: build, kafka-0.8, metrics > Attachments: kafka-fix-for-826.patch, kafka-fix-for-826-take2.patch > > > In order to mavenize Kafka 0.8, we have to depend on metrics 2.2.0 since > metrics 3.x is a huge change as well as not an officially supported release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-850) add an option to show under replicated partitions in list topic command
[ https://issues.apache.org/jira/browse/KAFKA-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-850: -- Attachment: kafka-850_v3.patch Attach patch v3 by also adding an option to show unavailable partitions. > add an option to show under replicated partitions in list topic command > --- > > Key: KAFKA-850 > URL: https://issues.apache.org/jira/browse/KAFKA-850 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 0.8 >Reporter: Jun Rao >Assignee: Jun Rao >Priority: Blocker > Attachments: kafka-850.patch, kafka-850_v2.patch, kafka-850_v3.patch > > > For debugging purpose, it's very important to be able to find out the under > replicated partitions quickly. List topic command is a good place to add this > feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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=13624220#comment-13624220 ] Scott Carey commented on KAFKA-717: --- To support all versions concurrently, we need a patch that moves the affected files to special directories per version. This s.o. question seems to have the most information I can find regarding the issue and how to solve it: http://stackoverflow.com/questions/13872226/how-to-support-multiple-scala-versions-in-a-library > scala 2.10 build support > > > Key: KAFKA-717 > URL: https://issues.apache.org/jira/browse/KAFKA-717 > Project: Kafka > Issue Type: Improvement > Components: packaging >Affects Versions: 0.8 >Reporter: Viktor Taranenko > Labels: build > Attachments: 0001-KAFKA-717-Convert-to-scala-2.10.patch, > kafka_scala_2.10.tar.gz > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-854) Upgrade dependencies for 0.8
[
https://issues.apache.org/jira/browse/KAFKA-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624250#comment-13624250
]
Scott Carey commented on KAFKA-854:
---
Also, upgrading log4j means that all of the ugly bits with:
{code}
//The issue is going from log4j 1.2.14 to 1.2.15, the developers added some
features which required
// some dependencies on various sun and javax packages.
override def ivyXML =
{ocde}
can go away, they made all of the funky dependencies "system" "provided", or
"optional" so they are not transitively pulled in (as they should have been to
begin with).
> Upgrade dependencies for 0.8
>
>
> Key: KAFKA-854
> URL: https://issues.apache.org/jira/browse/KAFKA-854
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Scott Carey
> Attachments: 0001-KAFKA-854-Upgrade-Deps-to-latest.patch
>
>
> Many of the dependencies that Kafka 0.8 uses are old. It would be a good
> idea to upgrade all of these where possible.
> log4j is set to 1.2.15, but the latest is 1.2.17
> zookeeper is at 3.3.4, , there is 3.3.6 (August 2012), and 3.4.5 (Nov 2012.
> 3.4.x includes several major enhancements and fixes over the 3.3.x line.
> org.slf4j is at 1.6.4, there is 1.6.6 (June 2012) and 1.7.5 (March 2013)
> net.sf.jopt-simple is at 3.2, there is 3.3 (May 2011) and 4.4 (Jan 2013)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-854) Upgrade dependencies for 0.8
[
https://issues.apache.org/jira/browse/KAFKA-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624255#comment-13624255
]
Scott Carey commented on KAFKA-854:
---
Why are dependencies repeated?
project/build/KafkaProject.scala defines:
{code}
trait CoreDependencies {
val log4j = "log4j" % "log4j" % "1.2.15"
val jopt = "net.sf.jopt-simple" % "jopt-simple" % "3.2"
val slf4jSimple = "org.slf4j" % "slf4j-simple" % "1.6.4"
}
{code}
and
project/Build.scala defines
{code}
libraryDependencies ++= Seq(
"log4j" % "log4j"% "1.2.15",
"net.sf.jopt-simple"% "jopt-simple" % "3.2",
"org.slf4j" % "slf4j-simple" % "1.6.4"
),
{code}
Likewise the hadoop settings are repeated.
> Upgrade dependencies for 0.8
>
>
> Key: KAFKA-854
> URL: https://issues.apache.org/jira/browse/KAFKA-854
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Scott Carey
> Attachments: 0001-KAFKA-854-Upgrade-Deps-to-latest.patch
>
>
> Many of the dependencies that Kafka 0.8 uses are old. It would be a good
> idea to upgrade all of these where possible.
> log4j is set to 1.2.15, but the latest is 1.2.17
> zookeeper is at 3.3.4, , there is 3.3.6 (August 2012), and 3.4.5 (Nov 2012.
> 3.4.x includes several major enhancements and fixes over the 3.3.x line.
> org.slf4j is at 1.6.4, there is 1.6.6 (June 2012) and 1.7.5 (March 2013)
> net.sf.jopt-simple is at 3.2, there is 3.3 (May 2011) and 4.4 (Jan 2013)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (KAFKA-854) Upgrade dependencies for 0.8
[
https://issues.apache.org/jira/browse/KAFKA-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624255#comment-13624255
]
Scott Carey edited comment on KAFKA-854 at 4/6/13 1:06 AM:
---
Why are dependencies repeated?
project/build/KafkaProject.scala defines:
{noformat}
trait CoreDependencies {
val log4j = "log4j" % "log4j" % "1.2.15"
val jopt = "net.sf.jopt-simple" % "jopt-simple" % "3.2"
val slf4jSimple = "org.slf4j" % "slf4j-simple" % "1.6.4"
}
{noformat}
and
project/Build.scala defines
{noformat}
libraryDependencies ++= Seq(
"log4j" % "log4j"% "1.2.15",
"net.sf.jopt-simple"% "jopt-simple" % "3.2",
"org.slf4j" % "slf4j-simple" % "1.6.4"
),
{noformat}
Likewise the hadoop settings are repeated.
was (Author: scott_carey):
Why are dependencies repeated?
project/build/KafkaProject.scala defines:
{code}
trait CoreDependencies {
val log4j = "log4j" % "log4j" % "1.2.15"
val jopt = "net.sf.jopt-simple" % "jopt-simple" % "3.2"
val slf4jSimple = "org.slf4j" % "slf4j-simple" % "1.6.4"
}
{code}
and
project/Build.scala defines
{code}
libraryDependencies ++= Seq(
"log4j" % "log4j"% "1.2.15",
"net.sf.jopt-simple"% "jopt-simple" % "3.2",
"org.slf4j" % "slf4j-simple" % "1.6.4"
),
{code}
Likewise the hadoop settings are repeated.
> Upgrade dependencies for 0.8
>
>
> Key: KAFKA-854
> URL: https://issues.apache.org/jira/browse/KAFKA-854
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Scott Carey
> Attachments: 0001-KAFKA-854-Upgrade-Deps-to-latest.patch
>
>
> Many of the dependencies that Kafka 0.8 uses are old. It would be a good
> idea to upgrade all of these where possible.
> log4j is set to 1.2.15, but the latest is 1.2.17
> zookeeper is at 3.3.4, , there is 3.3.6 (August 2012), and 3.4.5 (Nov 2012.
> 3.4.x includes several major enhancements and fixes over the 3.3.x line.
> org.slf4j is at 1.6.4, there is 1.6.6 (June 2012) and 1.7.5 (March 2013)
> net.sf.jopt-simple is at 3.2, there is 3.3 (May 2011) and 4.4 (Jan 2013)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (KAFKA-854) Upgrade dependencies for 0.8
[
https://issues.apache.org/jira/browse/KAFKA-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624255#comment-13624255
]
Scott Carey edited comment on KAFKA-854 at 4/6/13 1:07 AM:
---
Why are dependencies repeated?
project/build/KafkaProject.scala defines:
{quote}
trait CoreDependencies {
val log4j = "log4j" % "log4j" % "1.2.15"
val jopt = "net.sf.jopt-simple" % "jopt-simple" % "3.2"
val slf4jSimple = "org.slf4j" % "slf4j-simple" % "1.6.4"
}
{quote}
and
project/Build.scala defines
{quote}
libraryDependencies ++= Seq(
"log4j" % "log4j"% "1.2.15",
"net.sf.jopt-simple"% "jopt-simple" % "3.2",
"org.slf4j" % "slf4j-simple" % "1.6.4"
),
{quote}
Likewise the hadoop settings are repeated.
was (Author: scott_carey):
Why are dependencies repeated?
project/build/KafkaProject.scala defines:
{noformat}
trait CoreDependencies {
val log4j = "log4j" % "log4j" % "1.2.15"
val jopt = "net.sf.jopt-simple" % "jopt-simple" % "3.2"
val slf4jSimple = "org.slf4j" % "slf4j-simple" % "1.6.4"
}
{noformat}
and
project/Build.scala defines
{noformat}
libraryDependencies ++= Seq(
"log4j" % "log4j"% "1.2.15",
"net.sf.jopt-simple"% "jopt-simple" % "3.2",
"org.slf4j" % "slf4j-simple" % "1.6.4"
),
{noformat}
Likewise the hadoop settings are repeated.
> Upgrade dependencies for 0.8
>
>
> Key: KAFKA-854
> URL: https://issues.apache.org/jira/browse/KAFKA-854
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Scott Carey
> Attachments: 0001-KAFKA-854-Upgrade-Deps-to-latest.patch
>
>
> Many of the dependencies that Kafka 0.8 uses are old. It would be a good
> idea to upgrade all of these where possible.
> log4j is set to 1.2.15, but the latest is 1.2.17
> zookeeper is at 3.3.4, , there is 3.3.6 (August 2012), and 3.4.5 (Nov 2012.
> 3.4.x includes several major enhancements and fixes over the 3.3.x line.
> org.slf4j is at 1.6.4, there is 1.6.6 (June 2012) and 1.7.5 (March 2013)
> net.sf.jopt-simple is at 3.2, there is 3.3 (May 2011) and 4.4 (Jan 2013)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-854) Upgrade dependencies for 0.8
[ https://issues.apache.org/jira/browse/KAFKA-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624264#comment-13624264 ] Scott Carey commented on KAFKA-854: --- Ick, worse, some dependencies are listed three times -- once in SBT format, once in Maven XML format (bulky) and again Ivy xml fomat (yuck). The DRY principle gods are angry and are having their vengeance on any who wish to maintain this. > Upgrade dependencies for 0.8 > > > Key: KAFKA-854 > URL: https://issues.apache.org/jira/browse/KAFKA-854 > Project: Kafka > Issue Type: Improvement >Affects Versions: 0.8 >Reporter: Scott Carey > Attachments: 0001-KAFKA-854-Upgrade-Deps-to-latest.patch > > > Many of the dependencies that Kafka 0.8 uses are old. It would be a good > idea to upgrade all of these where possible. > log4j is set to 1.2.15, but the latest is 1.2.17 > zookeeper is at 3.3.4, , there is 3.3.6 (August 2012), and 3.4.5 (Nov 2012. > 3.4.x includes several major enhancements and fixes over the 3.3.x line. > org.slf4j is at 1.6.4, there is 1.6.6 (June 2012) and 1.7.5 (March 2013) > net.sf.jopt-simple is at 3.2, there is 3.3 (May 2011) and 4.4 (Jan 2013) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
