[
https://issues.apache.org/jira/browse/SAMZA-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15518605#comment-15518605
]
Nicolas Colomer commented on SAMZA-855:
---------------------------------------
> it will not be easy to package two different versions of Kafka client jars w/
> samza
Well I agree your point - even if we could imagine some kind of dependency
shading but It rarely is a good thing when it comes to that.
> Hence, I think that we will have to make the decision to move forward only.
I agree too.
To tell you more about our situation, we just achieved the migration of our
Kafka cluster from 0.8.2.2 to 0.10.0.1. It's still interacting with clients
(including samza) using the 0.8.x protocol (see related Kafka's Upgrade note at
https://kafka.apache.org/documentation.html#upgrade_10_performance_impact)
until we upgrade most of them to Kafka 10, from when we'll be able to
definitely bump up the protocol.
Since we extensively rely on Samza for critical production tasks, we need it to
be able to consume our new and shiny kafka 10 cluster :)
We'll start to do tests next week, I'll put feedbacks here as soon as we have.
> Upgrade Samza's Kafka client version to 0.10.0.0
> ------------------------------------------------
>
> Key: SAMZA-855
> URL: https://issues.apache.org/jira/browse/SAMZA-855
> Project: Samza
> Issue Type: Bug
> Reporter: Yi Pan (Data Infrastructure)
> Assignee: Robert Crim
>
> As Kafka 0.10.0.0 is out, we should upgrade Samza's client library to
> 0.10.0.0 to include the new consumer library and the bug fixes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
