Add number handling options to round/truncate decimals - #177
Merged
AdrianStrugala merged 2 commits intoSep 18, 2025
Merged
Conversation
Contributor
Author
|
@AdrianStrugala Any chance to take a look at this? |
AdrianStrugala
approved these changes
Sep 18, 2025
Owner
|
Hey, thank you for the PR. |
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
2 participants
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.
We find ourselves constantly hitting the error message that our decimals do not fit into the scale/precision of the defined Avro schema. This change adds an opt-in handling for decimals that fall outside of the decimal schema with either truncating or rounding.
The default behavior is preserved, so large decimals will continue to throw an exception when writing a decimal value.