[Doc] Add schema configuration to conf file and reference documentation #13983
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
@momo-jun Could you take a look? |
github-actions
bot
added
the
doc
Member
Author
|
/pulsarbot rerun-failure-checks |
momo-jun
reviewed
Jan 28, 2022
momo-jun
reviewed
Jan 28, 2022
momo-jun
reviewed
Jan 28, 2022
nodece
force-pushed
the
add_schema_conf
branch
3 times, most recently
from
9be79f5 to
ab01106
Compare
Contributor
|
@Anonymitaet Can you pls review this doc PR? |
nodece
force-pushed
the
add_schema_conf
branch
from
ab01106 to
79dcba4
Compare
Anonymitaet
reviewed
Jan 28, 2022
nodece
force-pushed
the
add_schema_conf
branch
from
79dcba4 to
7c8453b
Compare
Anonymitaet
reviewed
Feb 7, 2022
Member
Anonymitaet
left a comment
Anonymitaet
left a comment
There was a problem hiding this comment.
PTAL at my comments, thanks.
nodece
force-pushed
the
add_schema_conf
branch
from
6e8c975 to
3c5a586
Compare
Signed-off-by: Zixuan Liu <nodeces@gmail.com>
nodece
force-pushed
the
add_schema_conf
branch
from
3c5a586 to
baab87b
Compare
Member
Author
|
@Anonymitaet Sorry, I didn't notice the conflict. |
nodece
commented
Feb 7, 2022
| |isSchemaValidationEnforced|Enforce schema validation on following cases: if a producer without a schema attempts to produce to a topic with schema, the producer will be failed to connect. PLEASE be carefully on using this, since non-java clients don't support schema. If this setting is enabled, then non-java clients fail to produce.|false| | ||
| |isSchemaValidationEnforced| Whether to enable schema validation, when schema validation is enabled, if a producer without a schema attempts to produce the message to a topic with schema, the producer is rejected and disconnected.|false| | ||
| |isAllowAutoUpdateSchemaEnabled|Allow schema to be auto updated at broker level.|true| | ||
| |schemaCompatibilityStrategy| The schema compatibility strategy at broker level, see [here](schema-evolution-compatibility.md#schema-compatibility-check-strategy) for available values.|FULL| |
Member
Author
There was a problem hiding this comment.
Use URL to avoid duplicate descriptions of available values.
2 tasks
Member
Anonymitaet
approved these changes
Feb 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Motivation
Some documentation and config files miss the schema configuration.
Modifications
systemTopicSchemaCompatibilityStrategy,schemaCompatibilityStrategy,isSchemaValidationEnforcedandschemaRegistryStorageClassNametoconf/standalone.confreference-configuration.mdDocumentation
doc- This PR adds doc for [Broker] Fix read schema compatibility strategy priority #13938