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.

Sign up for GitHub

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

Jump to bottom

Pulsar schema api should respect to namespace level compatibility #4821

Closed
sijie opened this issue Jul 26, 2019 · 1 comment · Fixed by #4950
Closed

Pulsar schema api should respect to namespace level compatibility #4821

sijie opened this issue Jul 26, 2019 · 1 comment · Fixed by #4950
Labels
type/bug The PR fixed a bug or issue reported a bug
Milestone
2.5.0

Comments

@sijie
Copy link
Member

sijie commented Jul 26, 2019

Describe the bug
Currently the schema restful api is using SchemaCompatibilityStrategy.FULL

https://github.com/apache/pulsar/blob/master/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/v2/SchemasResource.java#L268

It should use the compatibility strategy configured at namespace level.
@sijie sijie added type/bug The PR fixed a bug or issue reported a bug component/schemaregistry labels Jul 26, 2019
@codelipenghui
Copy link
Contributor

@congbobo184 please take a look this issue

This was referenced Aug 14, 2019
Closed
Closed
Merged
sijie pushed a commit that referenced this issue Aug 22, 2019
@congbobo184 @sijie
Modify rest api post schema compatibility strategy (#4950)
958dcfe 
### Motivation
To fix #4821
@sijie sijie added this to the 2.5.0 milestone Sep 20, 2019
@sijie sijie mentioned this issue Sep 20, 2019
Closed
wolfstudy pushed a commit that referenced this issue Nov 20, 2019
@congbobo184 @wolfstudy
Modify rest api post schema compatibility strategy (#4950)
85a5b18 
### Motivation
To fix #4821 

(cherry picked from commit 958dcfe)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Milestone
2.5.0
2 participants
@sijie @codelipenghui