Uh oh!
There was an error while loading. Please reload this page.
[enhancement](maxcompute)support maxcompute timestamp column type. - #48768
Merged
Conversation
hello-stephen
commented
Mar 6, 2025
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
hubgeter
commented
Mar 6, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Mar 6, 2025
TPC-H: Total hot run time: 32802 ms |
doris-robot
commented
Mar 6, 2025
TPC-DS: Total hot run time: 185488 ms |
doris-robot
commented
Mar 6, 2025
ClickBench: Total hot run time: 31.29 s |
hubgeter
commented
Mar 6, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Mar 6, 2025
TPC-H: Total hot run time: 32230 ms |
doris-robot
commented
Mar 6, 2025
TPC-DS: Total hot run time: 192222 ms |
doris-robot
commented
Mar 6, 2025
ClickBench: Total hot run time: 30.65 s |
suxiaogang223
approved these changes
Mar 7, 2025
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
wuwenchi
approved these changes
Mar 7, 2025
github-actionsBot
pushed a commit
that referenced
this pull request
Mar 9, 2025
…48768) ### What problem does this PR solve? Problem Summary: 1. support maxcompute timestamp column type. 2. Add the parameter `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 insert `2023-02-02 00:00:00.123456789` into odps, doris will read it as `2023-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.
github-actionsBot
pushed a commit
that referenced
this pull request
Mar 9, 2025
…48768) ### What problem does this PR solve? Problem Summary: 1. support maxcompute timestamp column type. 2. Add the parameter `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 insert `2023-02-02 00:00:00.123456789` into odps, doris will read it as `2023-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.
hubgeter added a commit
to hubgeter/doris
that referenced
this pull request
Mar 12, 2025
…pache#48768) Problem Summary: 1. support maxcompute timestamp column type. 2. Add the parameter `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 insert `2023-02-02 00:00:00.123456789` into odps, doris will read it as `2023-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. (cherry picked from commit 2988dc3)
hubgeter added a commit
to hubgeter/doris
that referenced
this pull request
Mar 19, 2025
…pache#48768) Problem Summary: 1. support maxcompute timestamp column type. 2. Add the parameter `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 insert `2023-02-02 00:00:00.123456789` into odps, doris will read it as `2023-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. (cherry picked from commit 2988dc3)
hubgeter added a commit
to hubgeter/doris
that referenced
this pull request
Mar 27, 2025
…pache#48768) ### What problem does this PR solve? Problem Summary: 1. support maxcompute timestamp column type. 2. Add the parameter `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 insert `2023-02-02 00:00:00.123456789` into odps, doris will read it as `2023-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.
Merged
16 tasks
hubgeter added a commit
to hubgeter/doris
that referenced
this pull request
Mar 27, 2025
…pache#48768) Problem Summary: 1. support maxcompute timestamp column type. 2. Add the parameter `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 insert `2023-02-02 00:00:00.123456789` into odps, doris will read it as `2023-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. (cherry picked from commit 2988dc3)
csun5285 pushed a commit
to csun5285/doris
that referenced
this pull request
Mar 28, 2025
…n prune && timstamp type(apache#44508, apache#48768, apache#48325) (apache#3805) pick apache#44508apache#48768apache#48325 --------- Co-authored-by: zhangdong <zhangdong@selectdb.com>
hubgeter added a commit
to hubgeter/doris
that referenced
this pull request
Mar 28, 2025
…pache#48768) Problem Summary: 1. support maxcompute timestamp column type. 2. Add the parameter `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 insert `2023-02-02 00:00:00.123456789` into odps, doris will read it as `2023-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.
morningman pushed a commit
that referenced
this pull request
Mar 31, 2025
…f the timestamp data (#49600) ### What problem does this PR solve? Related pr : #48768 Problem Summary: When using the maxcompute storage api to read the mc timestamp column, if the timestamp precision is required to be at the nanosecond level, only data in the range of 1970-01-01 to 2038-01-19 can be read. Otherwise, an error will be reported: `ErrorCode=ODPS-0422214, ErrorMessage=ODPS-0422214: Read data failed - RuntimeTimestamp data overflow`. This pr changes the precision to milliseconds to solve this problem.
github-actionsBot
pushed a commit
that referenced
this pull request
Mar 31, 2025
…f the timestamp data (#49600) ### What problem does this PR solve? Related pr : #48768 Problem Summary: When using the maxcompute storage api to read the mc timestamp column, if the timestamp precision is required to be at the nanosecond level, only data in the range of 1970-01-01 to 2038-01-19 can be read. Otherwise, an error will be reported: `ErrorCode=ODPS-0422214, ErrorMessage=ODPS-0422214: Read data failed - RuntimeTimestamp data overflow`. This pr changes the precision to milliseconds to solve this problem.
github-actionsBot
pushed a commit
that referenced
this pull request
Mar 31, 2025
…f the timestamp data (#49600) ### What problem does this PR solve? Related pr : #48768 Problem Summary: When using the maxcompute storage api to read the mc timestamp column, if the timestamp precision is required to be at the nanosecond level, only data in the range of 1970-01-01 to 2038-01-19 can be read. Otherwise, an error will be reported: `ErrorCode=ODPS-0422214, ErrorMessage=ODPS-0422214: Read data failed - RuntimeTimestamp data overflow`. This pr changes the precision to milliseconds to solve this problem.
Closed
koarz pushed a commit
to koarz/doris
that referenced
this pull request
Jun 4, 2025
…pache#48768) ### What problem does this PR solve? Problem Summary: 1. support maxcompute timestamp column type. 2. Add the parameter `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 insert `2023-02-02 00:00:00.123456789` into odps, doris will read it as `2023-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.
koarz pushed a commit
to koarz/doris
that referenced
this pull request
Jun 4, 2025
…f the timestamp data (apache#49600) ### What problem does this PR solve? Related pr : apache#48768 Problem Summary: When using the maxcompute storage api to read the mc timestamp column, if the timestamp precision is required to be at the nanosecond level, only data in the range of 1970-01-01 to 2038-01-19 can be read. Otherwise, an error will be reported: `ErrorCode=ODPS-0422214, ErrorMessage=ODPS-0422214: Read data failed - RuntimeTimestamp data overflow`. This pr changes the precision to milliseconds to solve this problem.
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
Sign up for freeto 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?
Problem Summary:
mc.datetime_predicate_push_downto 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.123456789into 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
timestampcolumn type.Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)