-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[BugFix](MultiCatalog)fix iceberg table get split fail when with date type conjuct #30162
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
[BugFix](MultiCatalog)fix iceberg table get split fail when with date type conjuct #30162
Conversation
|
run buildall |
TPC-H: Total hot run time: 38786 ms |
TPC-DS: Total hot run time: 176857 ms |
ClickBench: Total hot run time: 31.48 s |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
morningman
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
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
morningman
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
|
run buildall |
TPC-H: Total hot run time: 39209 ms |
TPC-DS: Total hot run time: 186416 ms |
ClickBench: Total hot run time: 30.73 s |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
… to the target column (apache#32923) Convert the datetime type in the predicate according to the target column. And add a testcase for apache#32194 related apache#30478 apache#30162
Proposed changes
issue found in 2.0.4-rc05
1, have iceberg table with partitioned by date type column "day"
2 execute select * from test_table where day = "2022-01-01" will get nothing while the data exist in iceberg table, just we transfer the DateLiteral("2022-01-01") to datetime, cause we can not get the split correctly.
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...