momo-jun opened a new pull request, #18434:
URL: https://github.com/apache/pulsar/pull/18434

   
   ### Motivation
   
   <!-- Explain here the context, and why you're making that change. What is 
the problem you're trying to solve. -->
   
   This is a follow-up PR to https://github.com/apache/pulsar/pull/18242 to 
improve the Schema docs, aiming to provide Pulsar users with a more accurate, 
easy-to-read, and comprehensive information experience.
   
   ### Modifications
   
   <!-- Describe the modifications you've done. -->
   
   The content is revised and reviewed through [Google 
docs](https://docs.google.com/document/d/1YYansXopyVV66NaQ6TR9tfpq9MEhcbvCqv8ByFWuadA/edit?usp=sharing).
   1. Improve the description and illustrations of `How Pulsar schema works`.
   2. Add an illustration to introduce Pulsar schema.
   3. Incorporate `schema evolution` and subtopics into `Understand schema`.
   4. Relocate `native Avro` to `struct` schema.
   5. Add incremental changes to align with the code.
   6. Add/correct descriptions, commands, and code examples.
   7. Remove duplicate or redundant information.
   
   Many thanks to @congbobo184 and @RobertIndie for providing technical inputs 
and review comments.
   **The review is still in Process. Feel free to leave any comments.**
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [x] `doc` <!-- Your PR contains doc changes. Please attach the local 
preview screenshots (run `sh start.sh` at `pulsar/site2/website`) to your PR 
description, or else your PR might not get merged. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to