Skip to content
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.

Sign up for GitHub

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

Jump to bottom

branch-2.1: [enhancement](maxcompute)support maxcompute timestamp column type. #48768 #48842

Open
wants to merge 1 commit into
base: branch-2.1
Choose a base branch
from
Open

branch-2.1: [enhancement](maxcompute)support maxcompute timestamp column type. #48768 #48842

wants to merge 1 commit into from
+545 −12

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Mar 9, 2025

Cherry-picked from #48768

@hubgeter
[enhancement](maxcompute)support maxcompute timestamp column type. (#…
cb1851c 
…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.
@hello-stephen
Copy link
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring closed this Mar 9, 2025
@dataroaring dataroaring reopened this Mar 9, 2025
@hello-stephen
Copy link
Contributor

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@hello-stephen @dataroaring @hubgeter