fix(internal schema): changes to make internal schema registry more compatible with other schema registries #9636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/subjects/{subject}/versions/{version}
(getSchemaByVersion
) and/subjects/{subject}/versions
(listVersions
) which are used by Apache Gobblin to get the latest version of a registered schema. Since schema versions are always1
, these methods are rather straightforward.getSchemaByVersion
with version1
orlatest
returns the schema registered for a requested subject, otherwise it returns not found.listVersions
returns version1
if a schema registered with the requested subject exists, otherwise it returns not found.schemaType
, this field is not currently returned when an external Schema Registry is used and is thus removed from the response for compatibility. Additionally, the maxId field should only be returned when requested.Checklist