[Improve]:(MongoDB)optimize type inference to avoid unnecessary decimal conversion#596
Merged
Conversation
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
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.
Proposed changes
Previously, all numeric types were converted to Decimal to prevent precision loss when syncing mixed-type fields from MongoDB to Doris. This caused unnecessary precision degradation for single-type fields. For example, if the initial table has a small amount of data and an INT-type field with all values below 1000, after conversion to DECIMAL, the numeric precision will be limited to 3 digits. If the data evolves with business growth and the field value later exceeds 1000 (e.g., becomes a 4-digit number), it will lose precision due to the previously inferred limited length.
Problem Summary:
This commit improves the type inference logic:
Checklist(Required)
Further comments