[{"data":1,"prerenderedAt":450},["ShallowReactive",2],{"docs-nav":3,"docs-page-\u002Fdocs\u002Fschema-registry\u002Fnew-versions":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":77,"body":135,"description":441,"extension":442,"lastUpdated":443,"meta":444,"navTitle":78,"navigation":445,"order":21,"path":76,"seo":446,"sitemap":447,"stem":448,"__hash__":449},"docs\u002Fdocs\u002Fschema-registry\u002Fnew-versions.md",{"type":136,"value":137,"toc":431},"minimark",[138,147,152,158,165,174,177,181,184,253,261,265,268,271,275,282,285,293,299,303,306,360,367,374,380,385,389,392,405,408,412],[139,140,141,142,146],"p",{},"Use ",[143,144,145],"strong",{},"Register Schema"," for the first version of a new subject. To evolve an\nexisting subject, open it and publish a new version from its details.",[148,149,151],"h2",{"id":150},"register-avro-json-schema-and-protobuf-schemas","Register Avro, JSON Schema, and Protobuf schemas",[139,153,154,155,157],{},"Click ",[143,156,145],{},", then choose Avro, JSON Schema, or Protobuf. Kafma\nloads an editable example for the selected format.",[139,159,160,161,164],{},"Enter the schema definition and choose how its subject name is created. The\nsubject preview shows the exact name that will be registered. Click ",[143,162,163],{},"Register","\nto create the subject and its first version.",[139,166,167],{},[168,169],"img",{"alt":170,"height":171,"src":172,"width":173},"Kafma schema registration editor with Avro, JSON Schema, and Protobuf formats, subject naming strategy, and references",1268,"https:\u002F\u002Fmedia.kafma.app\u002Fdocs\u002Fschema-registry\u002Fnew-versions\u002Fcreate-schema.png",1820,[139,175,176],{},"If the subject already exists, Kafma stops the registration and directs you to\npublish a new version instead.",[148,178,180],{"id":179},"choose-a-kafka-subject-name-strategy","Choose a Kafka subject name strategy",[139,182,183],{},"The strategy controls which schemas share a version history.",[185,186,187,200],"table",{},[188,189,190],"thead",{},[191,192,193,197],"tr",{},[194,195,196],"th",{},"Strategy",[194,198,199],{},"Subject name",[201,202,203,221,231,243],"tbody",{},[191,204,205,211],{},[206,207,208],"td",{},[143,209,210],{},"Topic Name",[206,212,213,217,218],{},[214,215,216],"code",{},"\u003Ctopic>-key"," or ",[214,219,220],{},"\u003Ctopic>-value",[191,222,223,228],{},[206,224,225],{},[143,226,227],{},"Record Name",[206,229,230],{},"The qualified record or message name from the schema",[191,232,233,238],{},[206,234,235],{},[143,236,237],{},"Topic + Record Name",[206,239,240],{},[214,241,242],{},"\u003Ctopic>-\u003Cqualified-record-name>",[191,244,245,250],{},[206,246,247],{},[143,248,249],{},"Custom",[206,251,252],{},"The subject name you enter",[139,254,255,257,258,260],{},[143,256,210],{}," is the default and keeps key and value schemas separate for one\ntopic. Use a record-based strategy when the same record type appears across\ntopics or a topic contains multiple record types. Use ",[143,259,249],{}," when an\nexisting naming convention requires an exact subject name.",[148,262,264],{"id":263},"add-schema-references","Add schema references",[139,266,267],{},"A schema reference points to a type registered under another subject. Add the\nreference name as used by the schema, then enter its subject and version.",[139,269,270],{},"Every started reference must contain all three values. Kafma blocks\nregistration or publishing when a reference is incomplete; Schema Registry\nresolves the referenced definition when it validates the schema.",[148,272,274],{"id":273},"publish-a-new-schema-version","Publish a new schema version",[139,276,277,278,281],{},"Open a subject and select the version you want to use as the starting point.\nClick ",[143,279,280],{},"New Version"," to place that version beside an editable draft.",[139,283,284],{},"The comparison updates as you edit, making added and removed lines visible\nbefore publishing. You can also add, change, or remove references for the new\nversion.",[139,286,287],{},[168,288],{"alt":289,"height":290,"src":291,"width":292},"Kafma schema editor showing a draft diff against the selected schema version",1440,"https:\u002F\u002Fmedia.kafma.app\u002Fchangelog\u002Fv1.0.0\u002Fhomepage-schema.png",2414,[139,294,295,298],{},[143,296,297],{},"Publish"," becomes available after the draft has changed, its syntax can be\nparsed, and every reference is complete. Publishing registers the draft as the\nnext version under the same subject. Discarding the draft does not change\nSchema Registry.",[148,300,302],{"id":301},"schema-registry-compatibility","Schema Registry compatibility",[139,304,305],{},"Compatibility determines whether a schema can read data written with another\nversion registered under the subject.",[185,307,308,318],{},[188,309,310],{},[191,311,312,315],{},[194,313,314],{},"Mode",[194,316,317],{},"Compatibility direction",[201,319,320,330,340,350],{},[191,321,322,327],{},[206,323,324],{},[214,325,326],{},"BACKWARD",[206,328,329],{},"Consumers using the new schema can read data written with the previous schema",[191,331,332,337],{},[206,333,334],{},[214,335,336],{},"FORWARD",[206,338,339],{},"Consumers using the previous schema can read data written with the new schema",[191,341,342,347],{},[206,343,344],{},[214,345,346],{},"FULL",[206,348,349],{},"Both backward and forward compatibility",[191,351,352,357],{},[206,353,354],{},[214,355,356],{},"NONE",[206,358,359],{},"No compatibility check",[139,361,362,363,366],{},"Non-transitive modes compare the new schema with the latest registered version.\nThe ",[214,364,365],{},"_TRANSITIVE"," variants compare it with every earlier version. The exact\nallowed changes differ between Avro, JSON Schema, and Protobuf.",[139,368,369,370,373],{},"A subject override takes precedence over the global compatibility setting.\nCheck the ",[143,371,372],{},"Compatibility"," card in the subject details before changing a\nschema.",[139,375,376,377,379],{},"When you click ",[143,378,297],{},", Kafma checks compatibility as part of the publish\nflow; there is no separate check step. Schema Registry then validates the\nregistration and either accepts or rejects the new version.",[139,381,382,384],{},[214,383,356],{}," disables version-to-version compatibility checks. Schema Registry still\nvalidates the schema definition and its references.",[148,386,388],{"id":387},"fix-a-rejected-schema-version","Fix a rejected schema version",[139,390,391],{},"Start with the error shown above the draft, then check:",[393,394,395,399,402],"ol",{},[396,397,398],"li",{},"The subject's effective compatibility mode.",[396,400,401],{},"The lines added or removed in the comparison.",[396,403,404],{},"The name, subject, and version of each reference.",[139,406,407],{},"The selected version only sets the draft's starting point; it does not change\nwhich versions Schema Registry checks. Non-transitive modes check the latest\nversion, while transitive modes check all earlier versions. Use the\ncompatibility error and the highlighted changes beside the draft to identify\nwhat to revise.",[148,409,411],{"id":410},"next-steps","Next steps",[413,414,415,421,426],"ul",{},[396,416,417],{},[418,419,420],"a",{"href":73},"Browse Schema Registry subjects and versions",[396,422,423],{},[418,424,425],{"href":80},"Generate mock data and validate schemas",[396,427,428],{},[418,429,430],{"href":44},"Produce Avro and Protobuf Kafka messages",{"title":432,"searchDepth":26,"depth":26,"links":433},"",[434,435,436,437,438,439,440],{"id":150,"depth":21,"text":151},{"id":179,"depth":21,"text":180},{"id":263,"depth":21,"text":264},{"id":273,"depth":21,"text":274},{"id":301,"depth":21,"text":302},{"id":387,"depth":21,"text":388},{"id":410,"depth":21,"text":411},"Register Kafka schemas and publish new versions in Kafma. Manage Avro, JSON Schema, and Protobuf subjects in Kafka Schema Registry with compatibility checks.","md","2026-08-01",{},true,{"title":77,"description":441},{"loc":76},"docs\u002Fschema-registry\u002Fnew-versions","kb_RmkHuAAk1ayRZS8gZ6Lon_cntxJVYdqH7sZ0YKPc",1785561255867]