fix: filter null entries before creating KafkaConfigStore #3147
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.
Description
Our standalone module goes through
KafkaConfigStore
, which in turn usesImmutableMap
. TheImmutableMap
requires all values in a map to be non-null. Since we added a few configurations withnull
defaults - we need to filter them out here.Testing done
Updated tests to remove the
filterNullEntries
and manually spun up KSQL standalone.Reviewer checklist