Skip to content

DGS-19627 Fix JSON Schema validation to use latest schema if needed #2406

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

Merged
merged 2 commits into from
Jan 30, 2025

Conversation

rayokota
Copy link
Member

@rayokota rayokota commented Jan 29, 2025

What

Fix JSON Schema validation to use latest schema if needed.

Fixes #2401

Checklist

  • Contains customer facing changes? Including API/behavior changes
  • Did you add sufficient unit test and/or integration test coverage for this PR?
    • If not, please explain why it is not required

References

JIRA:

Test & Review

Open questions / Follow-ups

@rayokota rayokota requested review from a team as code owners January 29, 2025 01:29
@rayokota rayokota changed the title Fix JSON Schema validation DGS-19627 Fix JSON Schema validation to use latest schema if needed Jan 29, 2025
@sonarqube-confluent

This comment has been minimized.

Copy link
Member

@kcorman0 kcorman0 left a comment

Choose a reason for hiding this comment

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

thanks

@sonarqube-confluent
Copy link

Passed

Analysis Details

0 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 0 Code Smells

Coverage and Duplications

  • Coverage 95.50% Coverage (77.50% Estimated after merge)
  • Duplications No duplication information (0.00% Estimated after merge)

Project ID: confluent-kafka-dotnet

View in SonarQube

@rayokota rayokota merged commit 29995e6 into master Jan 30, 2025
2 checks passed
@rayokota rayokota deleted the fix-json-validation branch January 30, 2025 00:52
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.

Messages with wrong schema are successfully produced when UseLatestVersion = true
2 participants