Member since
04-02-2018
3
Posts
4
Kudos Received
0
Solutions
04-13-2018
06:15 PM
3 Kudos
After way too much struggling with the same issue, I was finally able to find the REST API URL. It was at http://localhost:<port>/swagger/. My Schema Registry was running on port 7788, so I could hit it from http://localhost:7788/swagger/ (remove the "/api" part of the url)
... View more
04-06-2018
07:39 PM
1 Kudo
Is it possible to change the type of a field in the schema registry? I created a schema in the registry, and it defaulted to backward compatibility. Right after I created it, I realized I mis-labeled one of the field types as a "long" when it was supposed to be "string." So {"name": "Emp_ID", "type": "long" } should instead be { "name": "Emp_ID", "type": "string"} Since the schema is set to backward compatibility, if I try to create a new version with the updated type, I get an error "reader type:STRING not compatible with writer type:LONG" so I'm unable to update the schema. Since there's not really a great way to delete schemas from the registry (aside from logging directly into the backing SQL database), I was hoping to be able to update the schema so it is still usable, rather than have a bunch of junk schemas that I can't use anymore. A colleague of mine said that with the confluent schema registry, they will disable compatibility checks, publish the new schema and then re-enable the compatibility as necessary. Is there a way to do something similar with Hortonworks Schema Registry? I haven't seen any setting that would allow me to change the compatibility mode. Thanks
... View more
Labels:
- Labels:
-
Schema Registry
04-06-2018
03:55 PM
I run into the same issue when I try to access the swagger documentation via /api/swagger. My current workaround is to reference the Confluent schema registry API docs here. The APIs aren't an exact 1:1 match, but many of the API calls are the same, so I was able to use that.
... View more