# Schema registry fails

**URL:** <https://discuss.akka.io/t/schema-registry-fails/6086>\
**Category:** Akka Libraries\
**Tags:** kafka\
**Created:** [March 11, 2020, 3:55pm UTC](https://discuss.akka.io/t/schema-registry-fails/6086 "2020-03-11T15:55:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raghav2211](https://avatars.discourse-cdn.com/v4/letter/r/e495f1/32.png) [@Raghav2211](https://discuss.akka.io/u/Raghav2211)\
**Post date:** [March 11, 2020, 3:55pm UTC](https://discuss.akka.io/t/schema-registry-fails/6086/1 "2020-03-11T15:55:20Z")

</div>

Hi there,  
I’ve a use case where I’m using alpakka-kafka to produce records on a topic with two avro schemas(HttpRequest & HttpResponse) with _ProducerMessage.single_ but if one of those schema is incorrect in schema registry then full stream close along with kafka producer in first message(if culprit is first one).  
So I think if i’ll send one type schema’s message to a topic then it’s ok but if i send multi schema on one topic then this is blocking other schema as well  
Is it design specific to close both(stream & kafka) on schema fails ?

Thanks

---

<div class="post-metadata">

**Author:** ![ennru](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.akka.io/ennru/32/1495_2.png) [@ennru](https://discuss.akka.io/u/ennru)\
**Post date:** [March 17, 2020, 7:09am UTC](https://discuss.akka.io/t/schema-registry-fails/6086/2 "2020-03-17T07:09:50Z")

</div>

Hi @Raghav2211

All Kafka serialisation errors will typically fail the whole Akka Stream.  
Errors from the Confluent Schema Registry serialisation and deserialisation are no different and not handled differently in Alpakka Kafka.

There is an idea to decouple the Schema Registry deserialisation from the Alpakka Consumer and Producer in [https://github.com/akka/alpakka-kafka/issues/965](https://github.com/akka/alpakka-kafka/issues/965)

Cheers,  
Enno.