You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Confluent's schema-registry creates a compacted topic called _schemas. On initial launch this works fine, but if the schema-registry is restarted, we get the following crash:
java.lang.NullPointerException
at io.confluent.kafka.schemaregistry.storage.KafkaStore.verifySchemaTopic(KafkaStore.java:263)
at io.confluent.kafka.schemaregistry.storage.KafkaStore.createOrVerifySchemaTopic(KafkaStore.java:171)
at io.confluent.kafka.schemaregistry.storage.KafkaStore.init(KafkaStore.java:118)
at io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry.init(KafkaSchemaRegistry.java:295)
at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.initSchemaRegistry(SchemaRegistryRestApplication.java:73)
at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.configureBaseApplication(SchemaRegistryRestApplication.java:88)
at io.confluent.rest.Application.configureHandler(Application.java:255)
at io.confluent.rest.ApplicationServer.doStart(ApplicationServer.java:227)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
at io.confluent.kafka.schemaregistry.rest.SchemaRegistryMain.main(SchemaRegistryMain.java:43)
I was able to reproduce this. The issue is that redpanda is not reporting the clean-up policy in the describe configs api. Should be an easy fix. @hagmonk i'll update this ticket when a fix drops.
hey @hagmonk a fix for this has merged. can you recommend any sort of workload / tests to run against the schema registry? given the feedback loop to get a new release cut with this change (@senior7515 ?) it could be useful for us to do a little testing locally in case there are other incompatibilities lurking in there.
Confluent's schema-registry creates a compacted topic called
_schemas
. On initial launch this works fine, but if the schema-registry is restarted, we get the following crash:Looking at KafkaStore.java:263, this occurs in
verifySchemaTopic
which is only called if the topic doesn't exist (see createOrVerifySchemaTopic)This problem persists even if the topic is manually created with
--compact
:Or modified with
set-config
:rpk debug info
The text was updated successfully, but these errors were encountered: