runtime: add materialize-kafka to ser_policy #1881
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
Kafka has a default maximum message size of 1MiB. This adds `materialize-kafka` to the list of connectors that use `ser_policy`, which should generally ensure that documents with individual extremely large string, array, or object fields don't exceed the message size limit for Kafka. This simple heuristic may not always be 100% what users desire, but in general it seems better to have the connector at least sort-of-work rather than crash in a way that would require a more complicated fix (possibly a derivation) to best support data exploration / PoC use cases.
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.
Description:
Kafka has a default maximum message size of 1MiB.
This adds
materialize-kafkato the list of connectors that useser_policy, which should generally ensure that documents with individual extremely large string, array, or object fields don't exceed the message size limit for Kafka.This simple heuristic may not always be 100% what users desire, but in general it seems better to have the connector at least sort-of-work rather than crash in a way that would require a more complicated fix (possibly a derivation) to best
support data exploration / PoC use cases.
Workflow steps:
(How does one use this feature, and how has it changed)
Documentation links affected:
(list any documentation links that you created, or existing ones that you've identified as needing updates, along with a brief description)
Notes for reviewers:
(anything that might help someone review this PR)
This change is