Remove check on Streams User deserialization that requires a topics.r…#540
Open
eazamaAU wants to merge 1 commit into
Open
Remove check on Streams User deserialization that requires a topics.r…#540eazamaAU wants to merge 1 commit into
eazamaAU wants to merge 1 commit into
Conversation
…ead block to be populated
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…ead block to be populated
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Removes a check in TopologyCustomDeserializer that throws an IOException if there are no READ_TOPICS.
What is the current behavior? (You can also link to an open issue here)
resolves Loosen Streams Deserialization Requirements Around Read Topics #539
If a Streams User has no READ_TOPICS configured, then an IOException is thrown
What is the new behavior (if this is a feature change)?
The check is removed and no IOException will be thrown
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No breaking changes
Other information:
N/A