You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yan Fang (JIRA)" <ji...@apache.org> on 2014/04/01 05:14:15 UTC
[jira] [Commented] (SAMZA-185) Upgrade Samza to Kafka 0.8.1
[ https://issues.apache.org/jira/browse/SAMZA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956056#comment-13956056 ]
Yan Fang commented on SAMZA-185:
--------------------------------
Hmm, it is weird. I guess this discussion is also out of the range of this issue. Since you can not reproduce my issue, currently (temperally), I will just build the latest Samza by removing the last test which has exceptions in my environment. Maybe dig into it when new clues come out. Thank you a lot !
> Upgrade Samza to Kafka 0.8.1
> ----------------------------
>
> Key: SAMZA-185
> URL: https://issues.apache.org/jira/browse/SAMZA-185
> Project: Samza
> Issue Type: Bug
> Components: build
> Affects Versions: 0.7.0
> Reporter: Chris Riccomini
> Labels: easyfix
> Attachments: SAMZA-185.1.patch, SAMZA-185.patch
>
>
> We should upgrade Kafka to 0.8.1. This involves:
> 1. Switch to using Kafka's maven dependencies (http://repo.maven.apache.org/maven2/org/apache//kafka/kafka_2.10/0.8.1/) instead of checking in JARs.
> 2. Upgrade build.gradle and gradle dependency versions to depend on 0.8.1.
> 3. Update index.md in docs to no longer say "It depends on a snapshot version of Kafka that will not officially be released for a few months."
--
This message was sent by Atlassian JIRA
(v6.2#6252)