-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Closed
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.MessagingMessaging crewMessaging crewSchema Registry
Milestone
Description
languages consensus on:
Methods
- get_schema
- return: data, class type
- Schema -> (content, SchemaProperties), SchemaProperties -> (id, version, …)
- return: data, class type
- get_schema_id
- return just id or all of the properties or new model class
Models
- Response type (naming)
- get_schema_id, return a string / SchemaId (class) / SchemaRepsonse / SchemaProperties
- get_schema, return a Schema
- any convention in the Python SDKs?
- SchemaProperties
- currently we have location_by_id, the swagger spec is Schema-Id-Location, should we align
- The swagger has Schema-Versions-Location, should we have this?
-JS has the schema properties: group, name, serialization_type, and content. This info seems like a better mapping in a cache to id? --> don't think this is true. as we discussed, JSSchemaDescriptiondoes not map to ourSchemaProperties, theirSchemaIddoes.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.MessagingMessaging crewMessaging crewSchema Registry