![]() ![]() Mostly curious if anyone has tried to swap out ByteArra圜onverter for AvroConverter The deserialization to do that lookup will fail (actually, the HTTP request to the registry) as this tool copied the Avro bytes, preserving the schema ID for topic A, but did not register those two new "subject" names in the destination registry.The destination consumers using KafkaAvroDeserializer are now expecting to do a lookup against the registry for subjects aggregate.A-key and aggregate.A-value,.Topic A is mirrored to DC2 cluster as aggregate.A.When produced to, a KafkaAvroSerializer class will create A-key and A-value "subjects" in the registry. Not sure if Comcast is using a Schema Registry such as those offered by Hortonworks or Confluent, but I'll walk over the scenario when you alter the topic-name on the destination cluster. Here's the documentation on Confluent Replicator about this setup. I would like to ask about the scenario when a Schema Registry has been deployed in two DC's. Good to see an open-source version of Confluent Replicator floating around.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |