Skip to content
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

[Schema] Schema compatibility strategy in broker level. #11856

Conversation

congbobo184
Copy link
Contributor

Motivation

link #11849
Schema compatibility strategy config in broker level.

implement

If namespace schema compatibility strategy is UNDEFINED, use broker schema compatibility strategy

Verifying this change

Add the tests for it

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

@congbobo184 congbobo184 requested review from codelipenghui, sijie, gaoran10 and eolivelli and removed request for sijie August 31, 2021 03:32
doc = "The schema compatibility strategy in broker level. If this config in namespace policy is `UNDEFINED`"
+ ", schema compatibility strategy check will use it in broker level."
)
private String schemaCompatibilityStrategy = "UNDEFINED";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we use the name of the enum SchemaCompatibilityStrategy.UNDEFINED.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good idea

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be able to directly use the enum type here

Copy link
Contributor

@gaoran10 gaoran10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Anonymitaet
Copy link
Member

Thanks for your contribution. For this PR, do we need to update docs?

(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

@congbobo184 congbobo184 added the doc-required Your PR changes impact docs and you will update later. label Sep 1, 2021
@congbobo184 congbobo184 merged commit b079c1e into apache:master Sep 1, 2021
hangc0276 pushed a commit that referenced this pull request Nov 4, 2021
## Motivation
link #11849
Schema compatibility strategy config in broker level.

## implement
If namespace schema compatibility strategy is `UNDEFINED`, use broker schema compatibility strategy

(cherry picked from commit b079c1e)
@hangc0276 hangc0276 added this to the 2.10.0 milestone Nov 4, 2021
@Anonymitaet Anonymitaet added doc-complete Your PR changes impact docs and the related docs have been already added. and removed doc-required Your PR changes impact docs and you will update later. labels Nov 19, 2021
@codelipenghui codelipenghui added cherry-picked/branch-2.9 Archived: 2.9 is end of life release/2.9.1 and removed release/2.9.2 labels Dec 20, 2021
@codelipenghui
Copy link
Contributor

@eolivelli This PR is already in branch-2.9 and will be released in 2.9.1. So I remove the label release/2.9.2

bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
## Motivation
link apache#11849 
Schema compatibility strategy config in broker level. 

## implement
If namespace schema compatibility strategy is `UNDEFINED`, use broker schema compatibility strategy
@congbobo184 congbobo184 deleted the congbobo184_broker_level_schema_SchemaCompatibilityStrategy branch March 24, 2022 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-picked/branch-2.8 Archived: 2.8 is end of life cherry-picked/branch-2.9 Archived: 2.9 is end of life doc-complete Your PR changes impact docs and the related docs have been already added. release/2.8.2 release/2.9.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants