This is related to https://github.com/Landoop/schema-registry-ui/issues/43, which was closed, but not resolved. The problem arises when a schema element refers to one defined above, as in the example shown below. This fails to validate in the UI, but will validate when posting the UI-generated CURL command from the command line.
This is related to https://github.com/Landoop/schema-registry-ui/issues/43, which was closed, but not resolved. The problem arises when a schema element refers to one defined above, as in the example shown below. This fails to validate in the UI, but will validate when posting the UI-generated CURL command from the command line.
[{ "namespace": "com.example", "name": "SearchRecordAttr", "type": "record", "fields":[ { "name": "productUrl", "type": "string" } ] }, { "namespace": "com.example", "name": "SearchRecord", "type": "record", "fields":[ { "name": "attributes", "default":null, "type": ["null", "SearchRecordAttr"]} ] }]