Fixes loss when serializing/deserializing large decimals #9180 (take 2) #9292
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.
Change Summary
Serializing/deserializing large decimal values is lossy. These changes enable expected behavior - no loss in information with large decimals.
Help Needed
I was able to solve the deserialization part. But I'm having trouble identifying how/where to control for model export to json (serialization is still lossy).<-- that message was on my work in the previous PR. Presently, am not sure where the interface to control serialization/deserialization. Could someone point me in the direction?Related issue number
fix #9180
Checklist