[RI-5545] [RI-5543] Add support for non-native big integers and allow non-native big integers for Vector formatting #3185
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.
Allow non-native big integers in JSONBigInt to convert large decimals. This can be the case for some language models that use large decimals in data. JSONBigInt will fall back to non-native big integers if they can't be packed in the native ones, so we still have support for the old ones. The support is explicitly added to Vector 32-bit and Vector 64-bit data.
When viewing some vector data that uses large numbers, which are often decimals, we try to pack them into javascript's native big int. Javascript's native big int doesn't support Big decimals yet. - sidorares/json-bigint#88
We have two options:
This PR chooses 1. Please check ticket comment.
Vector visualization
Data that can be packed into native big int
Data that are too large to be packed into native big Int