schema-registry-ui

552 views
Skip to first unread message

Antonios Chalkiopoulos

unread,
Jun 15, 2016, 5:16:21 AM6/15/16
to Confluent Platform
Using the schema-registry is transparent to developers, as  io.confluent.kafka.serializers.KafkaAvroSerializer takes care of registering, evolving, validating schemas etc


If you want to browse the schema-registry - understand how many schemas exist - how many versions - and how each version of your schemas look, have a look at:

 


It allows you to view existing schemas, search by subject name, or subject IDs, or even search within the schemas themselves

After building a UI - our team gained some extra insight into how confluent types internally work.

For example the Avro specification defines the int type - but not int8 or int16  
  
    "name": "usignal",
    "type": {
      "type": "int",
      "connect.type": "int16"
    }

The web UI is a single page app - that uses the REST Api of the schema-registry - that means that you you will need to enable CORS when using it


Regards, 
Antonios 

Ben Davison

unread,
Jun 15, 2016, 5:26:10 AM6/15/16
to confluent...@googlegroups.com
Awesome!

This was something missing from the schema registry. Have you checked out what uber has done with their schema registry (I think they have something custom, but it's the same basic concept)? You could probably get some neat ideas from it.

Ben

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/e68131f4-c4f9-4b39-b2af-5c3ef9924a69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.




This email, including attachments, is private and confidential. If you have received this email in error please notify the sender and delete it from your system. Emails are not secure and may contain viruses. No liability can be accepted for viruses that might be transferred by this email or any attachment. Any unauthorised copying of this message or unauthorised distribution and publication of the information contained herein are prohibited.

7digital Limited. Registered office: 69 Wilson Street, London EC2A 2BB.
Registered in England and Wales. Registered No. 04843573.

Antonios Chalkiopoulos

unread,
Jun 29, 2016, 1:43:43 PM6/29/16
to Confluent Platform
Hi,

Just released version schema-registry-ui v0.2 adding new features on routing, schema registration and compatibility checks

  https://github.com/landoop/schema-registry-ui

Ben, i didn't manage to see uber's schema-registry, maybe you can point me their direction ?!

Regards, Antonios

On Wednesday, 15 June 2016 10:26:10 UTC+1, Ben Davison wrote:
Awesome!

This was something missing from the schema registry. Have you checked out what uber has done with their schema registry (I think they have something custom, but it's the same basic concept)? You could probably get some neat ideas from it.

Ben
On Wed, Jun 15, 2016 at 10:16 AM, Antonios Chalkiopoulos <ant...@gmail.com> wrote:
Using the schema-registry is transparent to developers, as  io.confluent.kafka.serializers.KafkaAvroSerializer takes care of registering, evolving, validating schemas etc


If you want to browse the schema-registry - understand how many schemas exist - how many versions - and how each version of your schemas look, have a look at:

 


It allows you to view existing schemas, search by subject name, or subject IDs, or even search within the schemas themselves

After building a UI - our team gained some extra insight into how confluent types internally work.

For example the Avro specification defines the int type - but not int8 or int16  
  
    "name": "usignal",
    "type": {
      "type": "int",
      "connect.type": "int16"
    }

The web UI is a single page app - that uses the REST Api of the schema-registry - that means that you you will need to enable CORS when using it


Regards, 
Antonios 

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages