-
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
[enhancement](maxcompute)support maxcompute timestamp column type. #48768
base: master
Are you sure you want to change the base?
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
TPC-H: Total hot run time: 32802 ms
|
TPC-DS: Total hot run time: 185488 ms
|
ClickBench: Total hot run time: 31.29 s
|
run buildall |
TPC-H: Total hot run time: 32230 ms
|
TPC-DS: Total hot run time: 192222 ms
|
ClickBench: Total hot run time: 30.65 s
|
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. |
What problem does this PR solve?
Problem Summary:
mc.datetime_predicate_push_down
to disable predicate pushdown for odps catalog datetime type, because the timestamp precision of odps is 9, while the mapping precision of Doris is 6. If we insert2023-02-02 00:00:00.123456789
into odps, doris will read it as2023-02-02 00:00:00.123456
. Due to the lack of "789", we cannot push it down correctly. If you don't need such a high precision (greater than 6) on odps, it will not affect your normal use.Release note
support maxcompute
timestamp
column type.Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)