We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is a gap in the public methods provided by the schema registry client w.r.t. the REST API of Confluent Schema Registry.
In particular, it is not supported to list contexts. See API Reference: https://docs.confluent.io/platform/current/schema-registry/develop/api.html#get--contexts
In addition, the client does not allow to specify a base context path as described in https://docs.confluent.io/platform/current/schema-registry/schema-linking-cp.html#using-a-base-context-path to realize requests of the form GET <urls>/contexts/<context-id>/schemas/ids/<id>/versions
GET <urls>/contexts/<context-id>/schemas/ids/<id>/versions
Golang Interface of the client: https://github.com/confluentinc/confluent-kafka-go/blob/v2.3.0/schemaregistry/schemaregistry_client.go#L199
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This is a gap in the public methods provided by the schema registry client w.r.t. the REST API of Confluent Schema Registry.
In particular, it is not supported to list contexts.
See API Reference: https://docs.confluent.io/platform/current/schema-registry/develop/api.html#get--contexts
In addition, the client does not allow to specify a base context path as described in https://docs.confluent.io/platform/current/schema-registry/schema-linking-cp.html#using-a-base-context-path
to realize requests of the form
GET <urls>/contexts/<context-id>/schemas/ids/<id>/versions
Golang Interface of the client: https://github.com/confluentinc/confluent-kafka-go/blob/v2.3.0/schemaregistry/schemaregistry_client.go#L199
The text was updated successfully, but these errors were encountered: