[{"data":1,"prerenderedAt":371},["ShallowReactive",2],{"docs-nav":3,"docs-page-\u002Fdocs\u002Fschema-registry\u002Foverview":133},[4,27,53,68,83,98,117],{"slug":5,"label":6,"pages":7},"get-started","Get Started",[8,12,17,22],{"path":9,"title":10,"order":11},"\u002Fdocs","Welcome",0,{"path":13,"title":14,"navTitle":15,"order":16},"\u002Fdocs\u002Fget-started\u002Fquickstart","Quickstart",null,1,{"path":18,"title":19,"navTitle":20,"order":21},"\u002Fdocs\u002Fget-started\u002Fconnect-to-a-cluster","Connecting to a Kafka Cluster","Clusters",2,{"path":23,"title":24,"navTitle":25,"order":26},"\u002Fdocs\u002Fget-started\u002Flicense","Licensing and Activation","License",3,{"slug":28,"label":29,"pages":30},"console","Console",[31,35,39,43,48],{"path":32,"title":33,"navTitle":34,"order":16},"\u002Fdocs\u002Fconsole\u002Foverview","Produce and Consume Messages in the Kafka Console","Overview",{"path":36,"title":37,"navTitle":38,"order":21},"\u002Fdocs\u002Fconsole\u002Fconsuming-messages","Kafka Consumer: Reading Messages from a Topic","Consuming",{"path":40,"title":41,"navTitle":42,"order":26},"\u002Fdocs\u002Fconsole\u002Fdecoding-messages","Decoding Kafka Avro and Protobuf Messages","Decoding",{"path":44,"title":45,"navTitle":46,"order":47},"\u002Fdocs\u002Fconsole\u002Fproducing-messages","Kafka Producer: Sending Messages to a Topic","Producing",4,{"path":49,"title":50,"navTitle":51,"order":52},"\u002Fdocs\u002Fconsole\u002Freplay-forward-and-export","Replay and Export Kafka Messages","Replay & export",5,{"slug":54,"label":55,"pages":56},"topics","Topics",[57,60,64],{"path":58,"title":59,"navTitle":34,"order":16},"\u002Fdocs\u002Ftopics\u002Foverview","Browse and Inspect Kafka Topics",{"path":61,"title":62,"navTitle":63,"order":21},"\u002Fdocs\u002Ftopics\u002Fcreate-a-topic","Create a Kafka Topic: Partitions, Replication, and Retention","Create a topic",{"path":65,"title":66,"navTitle":67,"order":26},"\u002Fdocs\u002Ftopics\u002Fpartitions-and-records","Adding Kafka Partitions and Deleting Records","Partitions & records",{"slug":69,"label":70,"pages":71},"schema-registry","Schema Registry",[72,75,79],{"path":73,"title":74,"navTitle":34,"order":16},"\u002Fdocs\u002Fschema-registry\u002Foverview","Browse Kafka Schema Registry Subjects and Versions",{"path":76,"title":77,"navTitle":78,"order":21},"\u002Fdocs\u002Fschema-registry\u002Fnew-versions","Register Kafka Schemas and Publish New Versions","New versions",{"path":80,"title":81,"navTitle":82,"order":26},"\u002Fdocs\u002Fschema-registry\u002Fmock-and-lab","Avro Schema Validator and Mock Data Generator","Mock & Lab",{"slug":84,"label":85,"pages":86},"consumer-groups","Consumer Groups",[87,90,94],{"path":88,"title":89,"navTitle":34,"order":16},"\u002Fdocs\u002Fconsumer-groups\u002Foverview","Browse Kafka Consumer Groups and Assignments",{"path":91,"title":92,"navTitle":93,"order":21},"\u002Fdocs\u002Fconsumer-groups\u002Flag","Monitor Kafka Consumer Lag","Lag",{"path":95,"title":96,"navTitle":97,"order":26},"\u002Fdocs\u002Fconsumer-groups\u002Freset-offsets","Reset Kafka Consumer Group Offsets","Reset offsets",{"slug":99,"label":100,"pages":101},"data-clone","Data Clone",[102,105,109,113],{"path":103,"title":104,"navTitle":34,"order":16},"\u002Fdocs\u002Fdata-clone\u002Foverview","Clone Kafka Topics Between Clusters",{"path":106,"title":107,"navTitle":108,"order":21},"\u002Fdocs\u002Fdata-clone\u002Fscope-and-range","Configure Kafka Topic Cloning","Scope & range",{"path":110,"title":111,"navTitle":112,"order":26},"\u002Fdocs\u002Fdata-clone\u002Fmasking","Mask Sensitive Data in Kafka Messages","Masking",{"path":114,"title":115,"navTitle":116,"order":47},"\u002Fdocs\u002Fdata-clone\u002Fpre-flight","Run Pre-flight Checks Before a Kafka Data Clone","Pre-flight",{"slug":118,"label":119,"pages":120},"operate","Operate",[121,125,129],{"path":122,"title":123,"navTitle":124,"order":16},"\u002Fdocs\u002Foperate\u002Fbrokers","Inspect Kafka Brokers and Cluster Configuration","Brokers",{"path":126,"title":127,"navTitle":128,"order":21},"\u002Fdocs\u002Foperate\u002Faccess-control","Inspect Kafka ACLs and Simulate Access","Access Control",{"path":130,"title":131,"navTitle":132,"order":26},"\u002Fdocs\u002Foperate\u002Factivity-logs","Review Kafka Changes in Kafma Activity Logs","Activity Logs",{"id":134,"title":74,"body":135,"description":362,"extension":363,"lastUpdated":364,"meta":365,"navTitle":34,"navigation":366,"order":16,"path":73,"seo":367,"sitemap":368,"stem":369,"__hash__":370},"docs\u002Fdocs\u002Fschema-registry\u002Foverview.md",{"type":136,"value":137,"toc":353},"minimark",[138,142,147,150,153,204,207,210,214,217,230,233,242,245,249,252,263,271,274,294,301,305,308,315,318,323,327,330,333,337],[139,140,141],"p",{},"Kafma gives you one place to browse the subjects registered on a connection's\nSchema Registry. Open a subject in a full-width drawer to inspect its versions,\nschema IDs, fields, and compatibility.",[143,144,146],"h2",{"id":145},"what-is-a-kafka-schema-registry","What is a Kafka Schema Registry?",[139,148,149],{},"Kafka stores message keys and values as bytes. A Schema Registry stores the\nstructure used to serialize and deserialize those bytes, allowing producers and\nconsumers to agree on a format without placing the full schema in every record.",[139,151,152],{},"Three identifiers matter:",[154,155,156,169],"table",{},[157,158,159],"thead",{},[160,161,162,166],"tr",{},[163,164,165],"th",{},"Term",[163,167,168],{},"Meaning",[170,171,172,184,194],"tbody",{},[160,173,174,181],{},[175,176,177],"td",{},[178,179,180],"strong",{},"Subject",[175,182,183],{},"A named history of related schema versions",[160,185,186,191],{},[175,187,188],{},[178,189,190],{},"Version",[175,192,193],{},"A subject-local number assigned when a schema is registered",[160,195,196,201],{},[175,197,198],{},[178,199,200],{},"Schema ID",[175,202,203],{},"A registry-wide identifier for the registered schema",[139,205,206],{},"Versions are scoped to a subject. A schema ID is unique across the registry, but\nit is not exclusive to one subject. If two subjects register the same schema\ndefinition, Schema Registry returns the existing ID instead of creating a new\none, so both subjects use the same ID.",[139,208,209],{},"For records using the Confluent wire format, the producer writes the schema ID\nwith the payload. A consumer uses that ID to retrieve the matching schema and\ndecode the record.",[143,211,213],{"id":212},"browse-schema-registry-subjects","Browse Schema Registry subjects",[139,215,216],{},"The Schema Registry list shows each active subject with:",[218,219,220,224,227],"ul",{},[221,222,223],"li",{},"Its Avro, JSON Schema, or Protobuf format.",[221,225,226],{},"The latest active version and its schema ID.",[221,228,229],{},"The number of active versions.",[139,231,232],{},"Filter by subject name or format to narrow a large registry. Refresh the list\nwhen another application registers a schema, or pin a subject to the Watchlist\nfor faster access from Home.",[139,234,235],{},[236,237],"img",{"alt":238,"height":239,"src":240,"width":241},"Kafka Schema Registry list showing subjects, formats, latest schema versions, schema IDs, and active version counts",1440,"https:\u002F\u002Fmedia.kafma.app\u002Fdocs\u002Fschema-registry\u002Foverview\u002Fschema-list.png",1560,[139,243,244],{},"The list reflects active subjects and versions returned by the registry.\nPermanently deleted versions do not remain in this history.",[143,246,248],{"id":247},"inspect-schema-versions-and-fields","Inspect schema versions and fields",[139,250,251],{},"Select a subject to open its details in a full-width drawer over the Schema\nRegistry list. Close the drawer to return to the list. The summary shows the\nregistry mode, latest version, number of active versions, schema format, field\ncount, and effective compatibility level.",[139,253,254,255,258,259,262],{},"The version selector starts on the latest version and lets you inspect any\nactive version. The ",[178,256,257],{},"Schema"," tab places the registered source beside its parsed\nfields. When a version declares schema references, expand ",[178,260,261],{},"References"," to see\nthe referenced subject and version.",[139,264,265],{},[236,266],{"alt":267,"height":268,"src":269,"width":270},"Full-width Schema Registry subject drawer showing mode, versions, format, compatibility, schema source, and fields",1442,"https:\u002F\u002Fmedia.kafma.app\u002Fdocs\u002Fschema-registry\u002Foverview\u002Fschema-details.png",1542,[139,272,273],{},"The remaining tabs answer focused questions:",[218,275,276,282,288],{},[221,277,278,281],{},[178,279,280],{},"Mock"," generates a sample payload from the selected version.",[221,283,284,287],{},[178,285,286],{},"Lab"," validates a JSON payload against that version.",[221,289,290,293],{},[178,291,292],{},"Diff"," compares two active versions.",[139,295,296,297,300],{},"See ",[298,299,81],"a",{"href":80},"\nfor the Mock and Lab workflows.",[143,302,304],{"id":303},"set-schema-registry-compatibility","Set Schema Registry compatibility",[139,306,307],{},"The compatibility setting decides whether the registry accepts a new schema\nversion. Use the control at the top of the page to set the global default.\nSubjects that inherit this setting update with it.",[139,309,310,311,314],{},"A subject can override the global level. Open its drawer and use the edit icon\non the ",[178,312,313],{},"Compatibility"," card to choose an override, or reset the subject to\ninherit the global setting again. A global change does not replace a subject\noverride.",[139,316,317],{},"Compatibility and registry mode are separate. Compatibility evaluates a schema\nchange; mode controls whether the registry accepts writes at all. Kafma disables\nwrite actions on read-only connections and in non-writable registry modes.",[139,319,296,320,322],{},[298,321,77],{"href":76},"\nfor the compatibility levels and their effect on schema changes.",[143,324,326],{"id":325},"delete-a-schema-registry-subject","Delete a Schema Registry subject",[139,328,329],{},"Deleting a subject is permanent. Kafma first soft-deletes it, then permanently\ndeletes all subject-version registrations. After Schema Registry confirms the\ndeletion, Kafma removes the subject from the list and Watchlist.",[139,331,332],{},"This operation does not delete a Kafka topic or its messages. Before confirming,\ncheck whether producers, consumers, or other schemas still depend on the\nsubject. Deletion is unavailable on read-only connections and in non-writable\nregistry modes.",[143,334,336],{"id":335},"next-steps","Next steps",[218,338,339,343,348],{},[221,340,341],{},[298,342,77],{"href":76},[221,344,345],{},[298,346,347],{"href":80},"Generate mock data and validate schemas",[221,349,350],{},[298,351,352],{"href":40},"Decode Avro and Protobuf messages",{"title":354,"searchDepth":26,"depth":26,"links":355},"",[356,357,358,359,360,361],{"id":145,"depth":21,"text":146},{"id":212,"depth":21,"text":213},{"id":247,"depth":21,"text":248},{"id":303,"depth":21,"text":304},{"id":325,"depth":21,"text":326},{"id":335,"depth":21,"text":336},"Browse Kafka Schema Registry subjects and versions in Kafma. Inspect Avro, JSON Schema, and Protobuf schemas, schema IDs, and compatibility settings.","md","2026-08-01",{},true,{"title":74,"description":362},{"loc":73},"docs\u002Fschema-registry\u002Foverview","JvugrsXeMOz8JSLv85NXUkIIWxeHm0UnrPVGOeLrlvI",1785561255873]