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

[Schema Registry Avro] Remove backward compatibility in the first stable release #20063

Closed
deyaaeldeen opened this issue Jan 25, 2022 · 0 comments · Fixed by #20091 or #21648
Closed

[Schema Registry Avro] Remove backward compatibility in the first stable release #20063

deyaaeldeen opened this issue Jan 25, 2022 · 0 comments · Fixed by #20091 or #21648
Assignees
@deyaaeldeen
Labels
Schema Registry
Milestone
[2022] April

Comments

@deyaaeldeen
Copy link
Member

In the first stable release of the encoder, we expect customers to encode and decode messages that have been created by that stable encoder so the backward compatibility with beta.5 and earlier added in #20062 should be removed.
@deyaaeldeen deyaaeldeen added this to the [2022] March milestone Jan 25, 2022
@deyaaeldeen deyaaeldeen self-assigned this Jan 25, 2022
@deyaaeldeen deyaaeldeen mentioned this issue Jan 27, 2022
Merged
@deyaaeldeen deyaaeldeen reopened this Feb 2, 2022
@deyaaeldeen deyaaeldeen mentioned this issue Mar 3, 2022
Closed
5 tasks
@deyaaeldeen deyaaeldeen mentioned this issue Mar 16, 2022
Closed
5 tasks
@deyaaeldeen deyaaeldeen mentioned this issue Apr 27, 2022
Merged
3 tasks
deyaaeldeen added a commit that referenced this issue Apr 28, 2022
@deyaaeldeen
[Schema Registry Avro] Remove old format compatability (#21648)
61daf06 
### Packages impacted by this PR
@azure/schema-registry-avro

### Issues associated with this PR
Fixes #20063

### Describe the problem that is addressed by this PR
The old payload format was planned to be supported until the last beta before the first stable release and since the first stable release is scheduled for May, the compatability should be removed now.

### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?


### Are there test cases added in this PR? _(If not, why?)_


### Provide a list of related PRs _(if any)_


### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_

### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_
- [x] Added a changelog (if necessary)
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@deyaaeldeen deyaaeldeen

Labels
Schema Registry
Projects
None yet
Milestone
[2022] April
1 participant
@deyaaeldeen