-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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](cast datetime)add date like type coercion in legacy planner & result wrong with convert datetime to date predicate #39446
Open
mongo360
wants to merge
2
commits into
apache:branch-2.0
Choose a base branch
from
mongo360:branch-2.0_fix-dateliketype-coercion
base: branch-2.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
80c6c44
to
e8f21d5
Compare
run buildall |
TPC-H: Total hot run time: 49392 ms
|
TPC-DS: Total hot run time: 212836 ms
|
ClickBench: Total hot run time: 30.46 s
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
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
Problem 1
In legacy planner, the predicate like create_day <= '2024-08-08 23:59:59' will modify as cast (create_day as DATETIMEV2) <= '2024-08-08 23:59:59' when the column create_day is DATE; and this with cause the scan keys range not right in olap scan node.
Example
the profile:
Solution
When the predicate is like date column with datetime literal, modify datetime literal to column type in legacy planner same as nereids planner;
Problem 2
In legacy planner, and enable_date_conversion = false mode; result wrong with convert datetime to date condition.
Example
Solution
add cast to datetime same with 1.2;