Make Kafka schema registry an enum #427
Merged
Conversation
This file contains 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
jbeisen
force-pushed
the
kafka-schema-registry-enum
branch
from
9488ef0 to
406b14a
Compare
The JSON form in the console does not behave properly when an optional object has an optional field, which is the case with schema registry. Making it an enum in the schema solves it for this case.
jbeisen
force-pushed
the
kafka-schema-registry-enum
branch
from
406b14a to
aea50be
Compare
jacksonrnewhouse
approved these changes
Nov 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The JSON form in the console does not behave properly when an optional object has an optional field, which is the case with schema registry. Making it an enum in the schema solves it for this case.