[
https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709918#comment-13709918
]
Jay Kreps commented on KAFKA-717:
---------------------------------
Yeah I think we all want to do this, and likely it will work.
LinkedIn uses 2.8.0 and we can't upgrade our clients until all consumers are
upgraded. This is happening now but takes a while (we have hundreds of
applications) so we aren't going to be off 2.8.0 in the next few weeks for 0.8.
LinkedIn can do one of two things:
- Work off a local fork for linkedin temporarily for 0.8 so we can keep running
2.8
- Wait until 0.8.1 and let people who really want 2.10 apply the patch
Personally I think the project is better off with the later strategy so that
0.8 is getting any fixes from our production deploys, but you might disagree.
> 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-common-changes-for-2.10.patch,
> 0001-common-changes-for-2.10.patch,
> 0001-KAFKA-717-Convert-to-scala-2.10.patch,
> 0002-java-conversions-changes.patch, 0002-java-conversions-changes.patch,
> 0003-add-2.9.3.patch, 0003-add-2.9.3.patch,
> 0004-Fix-cross-compile-of-tests-update-to-2.10.2-and-set-.patch,
> KAFKA-717-complex.patch, KAFKA-717-simple.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
