[
https://issues.apache.org/jira/browse/SAMZA-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730708#comment-15730708
]
Yi Pan (Data Infrastructure) commented on SAMZA-855:
----------------------------------------------------
Hi, [~twbecker], we are planning to pull in Kafka 0.10 in the upcoming Samza
release (i.e. 0.12.0).
P.S. regarding to the multiple versions of Kafka libs, we had a discussion
earlier. The issue is not at the build time. The issue is in packaging. Right
now, the whole samza repo is packaged together and published as one .tgz file.
If we package multiple versions of Kafka libs in the samza release, there will
be a class name collision between old and new Kafka libs. One idea as a
long-term solution would be to package and release samza-core libs separately
from all pluggable implementation of SystemFactory and KeyValueStoreEngine,
etc., s.t. we can have different versions of KafkaSystemFactory in different
packages. We can discuss that more on a separate thread if that sounds
interesting to you.
Thanks!
> 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: Nicolas Colomer
> Fix For: 0.12.0
>
>
> 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)
