-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[feat][pip] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service #24328
New issue
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
Conversation
Denovo1998
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PIP looks meaningful.
Before this, a small trick by @lhotari inspired me.(#23794 (comment)) Now, I wrote PIP documentation through LLM.
This approach saves a lot of time, allowing us to focus on code development. The system prompt is as follows: https://gist.github.com/Denovo1998/163e55b3a612873364a00cf0df5a1b95 |
@Denovo1998 Nice work, I also improved the document with AI tools. /cc @BewareMyPower |
…with third-party schema registry service (apache#24328)
…with third-party schema registry service (apache#24328)



Motivation
The Pulsar client is better has the ability to access third-party schema registry service to manage the schema (register schema, get schema, validate schema, etc.). The schema registry service can be an independent service, if using an external schema registry service, the Pulsar broker doesn't need to care about the schema of the messages while creating producer or adding consumer subscription.
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes
Documentation
docdoc-requireddoc-not-neededdoc-complete