Merge pull request #4465 from jocelyndrean/sr-fix-duplicate-repro

SR - fix the duplicate of mutiple event types in the same topic
vdesabou · Oct 17, 2023 · 23592e1 · 23592e1
2 parents 2b52e14 + c7f74b5
commit 23592e1
Show file tree

Hide file tree

Showing 12 changed files with 20 additions and 136 deletions.
diff --git a/docs/content-template.md b/docs/content-template.md
@@ -323,7 +323,7 @@ There is also a Confluent Cloud version available [here](https://github.com/vdes
 
 ## 📝 Schema Registry
 - [How to produce Avro records via kafka-avro-console-producer with Union](https://github.com/vdesabou/kafka-docker-playground/tree/master/schema-registry/kafka-avro-console-producer-union) ![not tested](https://img.shields.io/badge/CI-not%20tested!-violet)
-- [Multiple event types in the same topic via Schema Registry API](https://github.com/vdesabou/kafka-docker-playground/tree/master/schema-registry/multiple-event-type-same-topic-api) ![not tested](https://img.shields.io/badge/CI-not%20tested!-violet)
+- [Multiple Event Types in the Same Topic](https://github.com/vdesabou/kafka-docker-playground/tree/master/schema-registry/multiple-event-types-in-topic) ![not tested](https://img.shields.io/badge/CI-not%20tested!-violet)
 - [How to use different Key and Value serializer with kafka-avro-console-producer](https://github.com/vdesabou/kafka-docker-playground/tree/master/schema-registry/use-diffrent-key-value-serializer-console-producer) ![not tested](https://img.shields.io/badge/CI-not%20tested!-violet)
 
 ## 👾 Other Playgrounds
@@ -337,7 +337,6 @@ There is also a Confluent Cloud version available [here](https://github.com/vdes
 - 👻 Testing [KIP-108](https://cwiki.apache.org/confluence/display/KAFKA/KIP-108%3A+Create+Topic+Policy) [Create Topic Policy](https://github.com/vdesabou/kafka-docker-playground/tree/master/other/create-topic-policy) ![not tested](https://img.shields.io/badge/CI-not%20tested!-violet)
 - 📉 [Monitoring Demo](https://github.com/vdesabou/kafka-docker-playground/tree/master/other/monitoring-demo) ![not tested](https://img.shields.io/badge/CI-not%20tested!-violet)
 - 🕵️‍♀️ [Kafka Connect Sink Monitoring Demo](https://github.com/vdesabou/kafka-docker-playground/tree/master/other/monitoring-sink-latency) Showcase different Kafka Connect Sink troubleshooting scenarios ![not tested](https://img.shields.io/badge/CI-not%20tested!-violet)
-- 🎫 [Multiple Event Types in the Same Topic](https://github.com/vdesabou/kafka-docker-playground/tree/master/other/multiple-event-types-in-topic) :other/multiple-event-types-in-topic:
 - 👊 [Integrate syslogs to detect SSH failure connections](https://github.com/vdesabou/kafka-docker-playground/tree/master/other/syslog-logstash-ksqldb) using Syslog source connector, LogStash and ksqlDB :other/syslog-logstash-ksqldb:
 - 📶 [How to ensure high availability of LDAP using DNS SRV Records](https://github.com/vdesabou/kafka-docker-playground/tree/master/other/ldap-authorizer-with-ldap-failover) :other/ldap-authorizer-with-ldap-failover:
 - 🕹 [AVRO examples](https://github.com/vdesabou/kafka-docker-playground/tree/master/other/schema-format-avro) including a JAVA producer :other/schema-format-avro:

diff --git a/schema-registry/kafka-avro-console-producer-union/README.md b/schema-registry/kafka-avro-console-producer-union/README.md
@@ -5,6 +5,25 @@
 With Apache Avro, you can set a field as an UNION of two types. A union datatype is used whenever the field has one or more datatypes. For example, ["null", "string"] declares a schema which may be either a null or string.
 
 Union type can be useful for Optional fields:
+```
+{
+  "type":"record",
+  "name":"myrecord",
+  "fields":[
+    { "name":"id", "type":"int"},
+    { "name":"product", "type":"string"},
+    { "name":"quantity", "type":"int"},
+    {
+      "name":"description",
+      "type":[
+        "null",
+        "string"
+      ],
+      "default":null
+    }
+  ]
+}
+```
 
 But it can be also useful for putting several Event Types in the same topic:
 ```

diff --git a/schema-registry/kafka-avro-console-producer-union/start.sh b/schema-registry/kafka-avro-console-producer-union/start.sh
@@ -27,7 +27,6 @@ docker exec -i connect kafka-avro-console-consumer --bootstrap-server broker:909
 
 
 # CASE 2 -> With Mutiple Event Types in the same Topic
-
 log "Register the Avro schema for Customer"
 # {
 #     "type": "record",

diff --git a/schema-registry/multiple-event-type-same-topic-api/README.md b/schema-registry/multiple-event-type-same-topic-api/README.md
diff --git a/schema-registry/multiple-event-type-same-topic-api/start.sh b/schema-registry/multiple-event-type-same-topic-api/start.sh
diff --git a/schema-registry/multiple-event-type-same-topic-api/stop.sh b/schema-registry/multiple-event-type-same-topic-api/stop.sh
diff --git a/...r/multiple-event-types-in-topic/README.md → ...y/multiple-event-types-in-topic/README.md b/...r/multiple-event-types-in-topic/README.md → ...y/multiple-event-types-in-topic/README.md
diff --git a/...ltiple-event-types-in-topic/alltypes.avsc → ...ltiple-event-types-in-topic/alltypes.avsc b/...ltiple-event-types-in-topic/alltypes.avsc → ...ltiple-event-types-in-topic/alltypes.avsc
diff --git a/...ltiple-event-types-in-topic/customer.avsc → ...ltiple-event-types-in-topic/customer.avsc b/...ltiple-event-types-in-topic/customer.avsc → ...ltiple-event-types-in-topic/customer.avsc
diff --git a/...ultiple-event-types-in-topic/product.avsc → ...ultiple-event-types-in-topic/product.avsc b/...ultiple-event-types-in-topic/product.avsc → ...ultiple-event-types-in-topic/product.avsc
diff --git a/...ltiple-event-types-in-topic/start-avro.sh → ...ltiple-event-types-in-topic/start-avro.sh b/...ltiple-event-types-in-topic/start-avro.sh → ...ltiple-event-types-in-topic/start-avro.sh
diff --git a/other/multiple-event-types-in-topic/stop.sh → ...try/multiple-event-types-in-topic/stop.sh b/other/multiple-event-types-in-topic/stop.sh → ...try/multiple-event-types-in-topic/stop.sh
-Original file line number
+Diff line change
@@ Expand Up @@
     # CASE 2 -> With Mutiple Event Types in the same Topic
     log "Register the Avro schema for Customer"
     # {
     #     "type": "record",
@@ Expand Down @@