Thank you for submitting this review request. Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.

The Architecture Board reviews Track 2 libraries only. If your library does not meet this requirement, please reach out to Architecture Board before creating the issue.

Please reference our review process guidelines to understand what is being asked for in the issue template.

To ensure consistency, all Tier-1 languages (C#, TypeScript, Java, Python) will generally be reviewed together. In expansive libraries, we will pair dynamic languages (Python, TypeScript) together, and strongly typed languages (C#, Java) together in separate meetings.

For Tier-2 languages (C, C++, Go, Android, iOS), the review will be on an as-needed basis.

Before submitting, ensure you adjust the title of the issue appropriately.

Note that the required material must be included before a meeting can be scheduled.

Contacts and Timeline

• Responsible service team: Schema Registry
• Main contacts: @deyaaeldeen
• Expected code complete date: 10/01/2021
• Expected release date: October milestone

About the Service

• Link to documentation introducing/describing the service: https://docs.microsoft.com/en-us/azure/event-hubs/schema-registry-overview
• Link to the service REST APIs: [Hub Generated] Review request for Microsoft.EventHub to add version preview/2021-11-01-preview azure-rest-api-specs#15855
• Link to GitHub issue for previous review sessions, if applicable: This package will implement caching so it will also benefit from Board Review: Caching responses in track 2 data-plane clients #3293.

About the client library

• Name of the client library: @azure/schema-registry
• Languages for this review: .NET, Java, JavaScript, and Python

Artifacts required (per language)

Please read through “API Review” section here to understand how these artifacts are generated. It is critical that these artifacts are present and are in the right format. If not, the language architects cannot review them with the SDK Team’s API review tool.

.NET

• APIView Link:
  SchemaRegistry
  Avro Serializer
• Link to Champion Scenarios/Quickstart samples:
  https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/schemaregistry/Azure.Data.SchemaRegistry/README.md
  https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/schemaregistry/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro/README.md

Java

• APIView Link:
  • azure-data-schemaregistry
  • azure-data-schemaregistry-avro
• Link to Champion Scenarios/Quickstart samples:
  • azure-data-schemaregistry
  • azure-data-schemaregistry-avro

Python

• APIView Link:
  • azure-schemaregistry
  • azure-schemaregistry-avroserializer
• Link to Champion Scenarios/Quickstart samples:
  • azure-schemaregistry
  • azure-schemaregistry-avroserializer

TypeScript

• APIView Link:
  • schema-registry
  • schema-registry-avro
• Link to Champion Scenarios/Quickstart samples:
  • schema-registry
  • schema-registry-avro

For all other languages, send a request to the Architecture Board to discuss the best format on individual basis.

Thank you!