You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2017/09/15 23:49:01 UTC
[jira] [Commented] (SAMZA-1418) Samza version 0.13.x doesn't start
with kafka version 0.11.0
[ https://issues.apache.org/jira/browse/SAMZA-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168692#comment-16168692 ]
Yi Pan (Data Infrastructure) commented on SAMZA-1418:
-----------------------------------------------------
[~nkbansal86], Samza 0.13 is built against Kafka 0.10.1.1. Are you trying to run it against a Kafka cluster w/ broker version 0.11? Normally, based on backward compatibility rules, it should still work (i.e. using a Kafka 0.10.1.1 client to connect to Kafka 0.11 broker). If you encounter any incompatibility issues, please let us know.
Thanks!
> Samza version 0.13.x doesn't start with kafka version 0.11.0
> ------------------------------------------------------------
>
> Key: SAMZA-1418
> URL: https://issues.apache.org/jira/browse/SAMZA-1418
> Project: Samza
> Issue Type: Bug
> Reporter: NAND KISHOR BANSAL
>
> I'm using following versions of different binaries of kafka and samza
> samza-api-0.13.0.jar
> samza-core_2.11-0.13.0.jar
> samza-kafka_2.11-0.13.0.jar
> samza-kv_2.11-0.13.0.jar
> samza-yarn_2.11-0.13.0.jar
> kafka_2.11-0.11.0.0.jar
> kafka-clients-0.11.0.0.jar
> But when starting the samza I hit following error:
> {code}
> Exception in thread "main" java.lang.NoSuchMethodError: kafka.api.TopicMetadata.errorCode()S
> at org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$12.apply(KafkaSystemAdmin.scala:361)
> at org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$12.apply(KafkaSystemAdmin.scala:360)
> at scala.collection.TraversableLike$$anonfun$flatMap$1.apply(TraversableLike.scala:241)
> at scala.collection.TraversableLike$$anonfun$flatMap$1.apply(TraversableLike.scala:241)
> at scala.collection.Iterator$class.foreach(Iterator.scala:893)
> at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
> at scala.collection.MapLike$DefaultValuesIterable.foreach(MapLike.scala:206)
> at scala.collection.TraversableLike$class.flatMap(TraversableLike.scala:241)
> at scala.collection.AbstractTraversable.flatMap(Traversable.scala:104)
> at org.apache.samza.system.kafka.KafkaSystemAdmin.org$apache$samza$system$kafka$KafkaSystemAdmin$$getTopicsAndPartitionsByBroker(KafkaSystemAdmin.scala:360)
> at org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2.apply(KafkaSystemAdmin.scala:220)
> at org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2.apply(KafkaSystemAdmin.scala:211)
> at org.apache.samza.util.ExponentialSleepStrategy.run(ExponentialSleepStrategy.scala:82)
> at org.apache.samza.system.kafka.KafkaSystemAdmin.getSystemStreamMetadata(KafkaSystemAdmin.scala:210)
> at org.apache.samza.system.kafka.KafkaSystemAdmin.getSystemStreamMetadata(KafkaSystemAdmin.scala:198)
> at org.apache.samza.coordinator.stream.CoordinatorStreamSystemConsumer.register(CoordinatorStreamSystemConsumer.java:93)
> at org.apache.samza.job.JobRunner.run(JobRunner.scala:97)
> at org.apache.samza.job.JobRunner$.doOperation(JobRunner.scala:52)
> at org.apache.samza.job.JobRunner$.main(JobRunner.scala:47)
> at org.apache.samza.job.JobRunner.main(JobRunner.scala)
> {code}
> I researched more and found out that a change made recently here: https://github.com/apache/kafka/commits/trunk/core/src/main/scala/kafka/api/TopicMetadata.scala
> which renamed {{TopicMetadata.errorCode}} to {{TopicMetadata.error}}
> but this change has not been accounted for in latest samza code.
> Samza file : https://github.com/apache/samza/blob/master/samza-kafka/src/main/scala/org/apache/samza/system/kafka/KafkaSystemAdmin.scala
> is still referring to {{TopicMetadata.errorCode}} variable
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)