[feat] Support AUTO_PUBLISH schema. #142
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Master Issue: apache/pulsar/pull/2685
Motivation
Implementing AUTO_PUBLISH schema solves the following problems:
If a schema exists in a topic, but the producer does not know it. He still wanted to send data to the topic. (The scenario in which the DLQ sends a message: Please refer [feat] Support Dead Letter Topic. #139 [Verifying this change][5])
For clients based on C++ implementations(Node and Python), these client supports help users serialize and deserialize.
They can use this
AUTO_PUBLISH
schema feature to implement the same semantics as Java clients.Modifications
AUTO_PUBLISH
schema, try to get the schema of that topic and use it.getSchema
onLookupService
(HTTP and Binary).Verifying this change
LookupServiceTest
unit test to covergetSchema
logic.SchemaTest.testAutoPublicSchema
unit test to cover creating producer success when the topic has a schema.Documentation
doc-required
(Your PR needs to update docs and you will update later)
doc-not-needed
(Please explain why)
doc
(Your PR contains doc changes)
doc-complete
(Docs have been already added)