When we parse schema that has the embedded schema and their namespaces are the same, currently namespace will exist in type when schema is merged, but if you parse that merged schema and send it to the schema registry, AvroSchema::parse($definition) will exclude that namespace from type.
When this kind of schema is merged it will result in having "type": "root.level.entity.embeddedSchema" but when parsed and sent to the registry it will have "type": "embeddedSchema"
I guess that this should be a part of --optimizeSubSchemaNamespaces option since it also excludes namespaces
When we parse schema that has the embedded schema and their namespaces are the same, currently namespace will exist in type when schema is merged, but if you parse that merged schema and send it to the schema registry,
AvroSchema::parse($definition)
will exclude that namespace from type.Example:
Root root.level.entity.schema-value.avsc
Embedded root.level.entity.embeddedSchema.avsc
When this kind of schema is merged it will result in having
"type": "root.level.entity.embeddedSchema"
but when parsed and sent to the registry it will have"type": "embeddedSchema"
I guess that this should be a part of --optimizeSubSchemaNamespaces option since it also excludes namespaces
@nick-zh what do you think?