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

Get effective compatibility level of subject #1150

Closed
wants to merge 1 commit into from

Conversation

shalinibani01
Copy link

This PR extends GET request to get effective compatibility level of a given subject.
The orginal issue is described here #1090.

Copy link

cla-assistant bot commented Mar 11, 2024

CLA assistant check
All committers have signed the CLA.

Copy link

cla-assistant bot commented Mar 11, 2024

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@@ -212,7 +212,7 @@ type Client interface {
GetAllSubjects() ([]string, error)
DeleteSubject(subject string, permanent bool) ([]int, error)
DeleteSubjectVersion(subject string, version int, permanent bool) (deletes int, err error)
GetCompatibility(subject string) (compatibility Compatibility, err error)
GetCompatibility(subject string, defaultToGlobal bool) (compatibility Compatibility, err error)

Choose a reason for hiding this comment

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

As discussed, this might break existing code because the function signature changes.

Choose a reason for hiding this comment

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

@rayokota can you comment on that?

var result compatibilityLevel
err = c.restService.handleRequest(newRequest("GET", subjectConfig, nil, url.PathEscape(subject)), &result)
err = c.restService.handleRequest(newRequest("GET", subjectConfigDefaultToGlobal, nil,

Choose a reason for hiding this comment

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

Here, this would change requests for the existing code in a way that ?defaultToGlobal=false is always appended. This should not cause issues (e.g. older versions of schema registry that might not know this parameter?).

@rayokota
Copy link
Member

Thanks @shalinibani01 , I believe this PR is subsumed by #1149

@shalinibani01
Copy link
Author

Thanks @shalinibani01 , I believe this PR is subsumed by #1149

Thanks! Since the changes that are present in this PR are already present in yours, I am closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants