Dinf 2950 Fix schema prefix removal and ensure consistent topic name tranformation #1471
+120
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes the schema subject mismatch issue by removing environment prefixes (like
development.orstaging.) from topic names before performing schema lookup.Key Changes
SchemaRegistrySerde.javato strip environment prefix before schema lookup.TopicsExporter.javato maintain consistent topic name transformation logic.SchemaRegistrySerdeTest.javato validate schema retrieval, serialization/deserialization, and environment prefix removal.Validation
Ran Gradle tests successfully — all unit tests passed, including
SchemaRegistrySerdeTest.Verified Kafka UI can now correctly deserialize schemas for environment-prefixed topics.
Confirmed that schema subjects match as expected after the fix.
Impact
Ensures consistent schema lookup across all environments and prevents
NOT FOUNDerrors during deserialization.