Skip to content

Conversation

@gaoran10
Copy link
Contributor

@gaoran10 gaoran10 commented May 21, 2025

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

  • Dependencies (add or upgrade a dependency)
  • The public API
  • The schema
  • The default values of configurations
  • The threading model
  • The binary protocol
  • The REST endpoints
  • The admin CLI options
  • The metrics
  • Anything that affects deployment

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

@github-actions github-actions bot added PIP doc-not-needed Your PR changes do not impact docs labels May 21, 2025
@gaoran10 gaoran10 self-assigned this May 21, 2025
Copy link
Contributor

@Denovo1998 Denovo1998 left a 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.

@BewareMyPower
Copy link
Contributor

BTW, you can leverage AI tool (e.g. Copilot) to improve the documents with more professional expression.

image

@Denovo1998
Copy link
Contributor

BTW, you can leverage AI tool (e.g. Copilot) to improve the documents with more professional expression.

image

@BewareMyPower @gaoran10

Before this, a small trick by @lhotari inspired me.(#23794 (comment))

Now, I wrote PIP documentation through LLM.


CleanShot 2025-06-13 at 20 05 18@2x


  • First, we need a good system prompt that can directly generate content output that meets the format requirements based on the article title in the PIP document.
  • We need to provide sufficient contextual information (e.g., code patches, the motivation for writing this PIP), so that the generated draft can reach a basic usable level. After multiple rounds of dialogue adjustments or manual modifications, the document will become very professional.

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

@gaoran10
Copy link
Contributor Author

@BewareMyPower @gaoran10

Before this, a small trick by @lhotari inspired me.(#23794 (comment))

Now, I wrote PIP documentation through LLM.

@Denovo1998 Nice work, I also improved the document with AI tools. /cc @BewareMyPower

@gaoran10 gaoran10 marked this pull request as draft June 27, 2025 02:54
@gaoran10 gaoran10 marked this pull request as ready for review July 6, 2025 17:35
@gaoran10 gaoran10 marked this pull request as draft July 11, 2025 16:12
@gaoran10 gaoran10 marked this pull request as ready for review August 12, 2025 11:02
@gaoran10 gaoran10 closed this Aug 13, 2025
@gaoran10 gaoran10 reopened this Aug 13, 2025
@BewareMyPower BewareMyPower merged commit 99535a6 into apache:master Aug 15, 2025
20 checks passed
@coderzc coderzc added this to the 4.1.0 milestone Sep 8, 2025
KannarFr pushed a commit to CleverCloud/pulsar that referenced this pull request Sep 22, 2025
walkinggo pushed a commit to walkinggo/pulsar that referenced this pull request Oct 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc-not-needed Your PR changes do not impact docs PIP

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants