-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[Fix](Variant) fix variant with not null #32248
Conversation
Thank you for your contribution to Apache Doris. |
ignore null bitmap for not null and make subcolumn access slots always nullable
b669057
to
f1f5f1d
Compare
run buildall |
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 38275 ms
|
slotDescriptor.setMaterializedColumnName(slotRef.getColumnName() | ||
+ "." + String.join(".", slotReference.getSubColPath())); | ||
// always nullable at present | ||
slotDescriptor.setIsNullable(true); |
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.
if variant slot always nullable, u should set it correctly in Nereids, because nereids need nullable info todo some optimization. if u set uncorrect nullable info, we will get wrong plan sometimes
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.
fixed
run buildall |
TPC-H: Total hot run time: 38316 ms
|
TeamCity be ut coverage result: |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
run p0 |
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
ignore null bitmap for not null and make subcolumn access slots always nullable
ignore null bitmap for not null and make subcolumn access slots always nullable
ignore null bitmap for not null and make subcolumn access slots always nullable
Proposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...