Hortonworks registry is confusing. I'm trying to deserialize avro messages so I registered my schema registry url as http://host.name:9090 and I can ping this url but not http://host.name:9090/api/v1!

pradeepcheers — Fri, 20 Oct 2017 05:09:15 GMT

Re: Hortonworks registry is confusing. I'm trying to deserialize avro messages so I registered my schema registry url as http://host.name:9090 and I can ping this url but not http://host.name:9090/api/v1!

ssahi — Sat, 21 Oct 2017 04:43:10 GMT

I'm not sure if you are using the default ports, or whether you have customized some of the ports. 9090 is usually the port for NiFi and not the schema registry. Schema Registry's default port, I think, is 7788. In addition, the Schema Registry has a very cool built-in tool to help making working with the APIs much easier. Try http://host.name:7788/api/swagger in a web browser, and see if the tool comes up, and go from there.

Hope this helps

question Hortonworks registry is confusing. I'm trying to deserialize avro messages so I registered my schema registry url as http://host.name:9090 and I can ping this url but not http://host.name:9090/api/v1! in Archives of Support Questions (Read Only)

Hortonworks registry is confusing. I'm trying to deserialize avro messages so I registered my schema registry url as http://host.name:9090 and I can ping this url but not http://host.name:9090/api/v1!

Re: Hortonworks registry is confusing. I'm trying to deserialize avro messages so I registered my schema registry url as http://host.name:9090 and I can ping this url but not http://host.name:9090/api/v1!