Skip to content

branch-2.1: [fix](mc)Fixed the issue that maxcompute catalog can only read part of the timestamp data #49600 #49706

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
Merged
yiguolei merged 1 commit into from
Apr 1, 2025
Merged

branch-2.1: [fix](mc)Fixed the issue that maxcompute catalog can only read part of the timestamp data #49600 #49706

yiguolei merged 1 commit into from
Apr 1, 2025
+110 −48

Conversation

@github-actions
Copy link
Contributor

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

Cherry-picked from #49600

@hubgeter
[fix](mc)Fixed the issue that maxcompute catalog can only read part o…
9cfad0f 
…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-actions github-actions bot requested a review from yiguolei as a code owner March 31, 2025 09:42
@Thearas
Copy link
Contributor

Thearas commented Mar 31, 2025

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 reopened this Mar 31, 2025
@Thearas
Copy link
Contributor

Thearas commented Mar 31, 2025

run buildall

@yiguolei yiguolei merged commit e898dbb into branch-2.1 Apr 1, 2025
20 checks passed
@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Apr 1, 2025
@github-actions
Copy link
Contributor Author

github-actions bot commented Apr 1, 2025

PR approved by at least one committer and no changes requested.

@github-actions github-actions bot deleted the auto-pick-49600-branch-2.1 branch April 1, 2025 09:09
@github-actions
Copy link
Contributor Author

github-actions bot commented Apr 1, 2025

PR approved by anyone and no changes requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@Thearas @yiguolei @dataroaring @hubgeter