New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoSuchMethodError: AbstractKafkaAvroDeserializer.executeRules #12785
Comments
This usually indicates a version conflict. How do you build the Pinot? Can you please check if you are using a different version of confluent Kafka? |
yes, I think that is the case. Those kafka brokers are running an old version of Kafka: 2.4.1 |
I have moved the Kafka Topic to another Cluster running kafka_2.13-3.1.1 and the issue persists. I have updated my Pinot deployment to "1.2.0-SNAPSHOT-13673f11508f00ae35f5bb12f9cf97b6897ebfba" on Kubernetes using the Helm attached. This is the output of the "version" REST method: { |
I'm also getting this error when I build from master. 1.1 release branch works fine.
|
On Pinot version 1.2.0-SNAPSHOT-3697552290f64b62e938152b891764adfb0ee031
We get a NoSuchMethodError when ingesting Avro messages from Kafka.
The same configuration works fine on Pinot version 1.0.0
1 2024-04-03T10:26:01.458004170+00:00 stderr F at java.base/java.lang.Thread.run(Thread.java:829)
2024-04-03 12:26:01.611 2024-04-03T10:26:01.458004170+00:00 stderr F at org.apache.pinot.core.data.manager.realtime.RealtimeSegmentDataManager$PartitionConsumer.run(RealtimeSegmentDataManager.java:703)
2024-04-03 12:26:01.611 2024-04-03T10:26:01.458004170+00:00 stderr F at org.apache.pinot.core.data.manager.realtime.RealtimeSegmentDataManager.consumeLoop(RealtimeSegmentDataManager.java:465)
2024-04-03 12:26:01.611 2024-04-03T10:26:01.458004170+00:00 stderr F at org.apache.pinot.core.data.manager.realtime.RealtimeSegmentDataManager.processStreamEvents(RealtimeSegmentDataManager.java:576)
2024-04-03 12:26:01.611 2024-04-03T10:26:01.458004170+00:00 stderr F at org.apache.pinot.spi.stream.StreamDataDecoderImpl.decode(StreamDataDecoderImpl.java:54)
2024-04-03 12:26:01.611 2024-04-03T10:26:01.458004170+00:00 stderr F at org.apache.pinot.plugin.inputformat.avro.confluent.KafkaConfluentSchemaRegistryAvroMessageDecoder.decode(KafkaConfluentSchemaRegistryAvroMessageDecoder.java:53)
2024-04-03 12:26:01.611 2024-04-03T10:26:01.458004170+00:00 stderr F at org.apache.pinot.plugin.inputformat.avro.confluent.KafkaConfluentSchemaRegistryAvroMessageDecoder.decode(KafkaConfluentSchemaRegistryAvroMessageDecoder.java:121)
2024-04-03 12:26:01.610 2024-04-03T10:26:01.458004170+00:00 stderr F at org.apache.pinot.plugin.inputformat.avro.confluent.KafkaConfluentSchemaRegistryAvroMessageDecoder.decode(KafkaConfluentSchemaRegistryAvroMessageDecoder.java:111)
2024-04-03 12:26:01.610 2024-04-03T10:26:01.458004170+00:00 stderr F at io.confluent.kafka.serializers.KafkaAvroDeserializer.deserialize(KafkaAvroDeserializer.java:103)
2024-04-03 12:26:01.610 2024-04-03T10:26:01.458004170+00:00 stderr F at io.confluent.kafka.serializers.KafkaAvroDeserializer.deserialize(KafkaAvroDeserializer.java:108)
2024-04-03 12:26:01.610 2024-04-03T10:26:01.458004170+00:00 stderr F at io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer.deserialize(AbstractKafkaAvroDeserializer.java:188)
2024-04-03 12:26:01.610 2024-04-03T10:26:01.458004170+00:00 stderr F at io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer$DeserializationContext.read(AbstractKafkaAvroDeserializer.java:532)
2024-04-03 12:26:01.610 2024-04-03T10:26:01.458004170+00:00 stderr F Exception in thread "sbts_edr_dlr__25__0__20240403T1024Z" java.lang.NoSuchMethodError: 'java.lang.Object io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer.executeRules(java.lang.String, java.lang.String, org.apache.pinot.shaded.org.apache.kafka.common.header.Headers, java.lang.Object, io.confluent.kafka.schemaregistry.client.rest.entities.RuleMode, io.confluent.kafka.schemaregistry.ParsedSchema, io.confluent.kafka.schemaregistry.ParsedSchema, java.lang.Object)'
2024-04-03 12:26:01.61
The text was updated successfully, but these errors were encountered: