-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](variant) Fix metadata compatibility for FE #53748
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 32798 ms |
TPC-DS: Total hot run time: 198052 ms |
ClickBench: Total hot run time: 28.76 s |
Contributor
FE UT Coverage ReportIncrement line coverage |
morrySnow
approved these changes
Jul 23, 2025
eldenmoon
reviewed
Jul 23, 2025
Member
eldenmoon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
csun5285
added a commit
to csun5285/doris
that referenced
this pull request
Jul 30, 2025
### What problem does this PR solve? - In version 3.1, we used 'VariantType', which inherits from 'ScalarType', as the metadata storage for newly created variants, differing from the previously used 'ScalarType'. - To ensure compatibility with previous metadata, convert 'VariantType' to 'ScalarType' before use.
csun5285
added a commit
to csun5285/doris
that referenced
this pull request
Jul 30, 2025
…2927) 1. support when the sub-columns in the specified variant are of a fixed type, these sub-columns can be included in sparse columns. 2. add many cases and ut branch-3.1: [fix](variant type) fix add variant column, index (apache#53092) [fix](variant) Fix metadata compatibility for FE (apache#53748) - In version 3.1, we used 'VariantType', which inherits from 'ScalarType', as the metadata storage for newly created variants, differing from the previously used 'ScalarType'. - To ensure compatibility with previous metadata, convert 'VariantType' to 'ScalarType' before use. fix [fix](variant) fix array contains null fix case fix
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.
What problem does this PR solve?
VariantType, which inherits fromScalarType, as the metadata storage for newly created variants, differing from the previously usedScalarType.VariantTypetoScalarTypebefore use.Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)