Satish Duggana

>Compatibility is not checked on import (whilst it is set on the broker), this is to avoid issues, we have to assume its been pre-checked, as historically during phases it...

OK. We do not support updating compatibility for now. Currently new version of schema validates compatibility against all the earlier versions. We may need to do add this if it...

Filed #171 for the validateAll and validateLatest to support Confluent SR migration.

@michaelandrepearce @harshach I am fine with this as temporary solution till we finalize on better solution if possible.

@radai-rosenblatt Fingerprint is used in finding out whether the same effective schema w.r.t compatibility already exists in registry with the same schema name, before it is added as new version....

@michaelandrepearce +1 to make client module having minimal dependencies. Ideally, common-server should not depend upon common-client but both can have dependencies on a single common module. It should also be...

Currently, schema name(in schema metadata) should be unique across the registry irrespective of the group. When a schema metadata with the given schema name is already given then it returns...

Having uniqueness with schema name and group gives separation of schemas at group level. We have started with that separation but I guess it was decided users can have naming...

@michaelandrepearce I have put my comments in #166 cc @harshach

I will take a look at this PR by ~~5th~~ /7th.