Skip to content

branch-4.0: [fix](catalog) update the table's last update time after related operations. (#59387) #59695

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
Open
morningman wants to merge 1 commit into
base: branch-4.0
Choose a base branch
from
Open

branch-4.0: [fix](catalog) update the table's last update time after related operations. (#59387) #59695

morningman wants to merge 1 commit into from

Conversation

@morningman
Copy link
Contributor

@morningman morningman commented Jan 8, 2026

bp (#59387)

@morningman
[fix](catalog) update the table's last update time after related oper…
7e2d8d1 
…ations. (apache#59387)

We should update the external table's last update time after operations
like schema change, insert or refresh.
So the the SQL cache feature can get the right time to validate the
cache.

Also merge `schemaUpdateTime` and `eventUpdateTime` into one
`updateTime`, and move it to `ExternalTable`.
So that all kinds of external table can use this field.
@morningman morningman requested a review from yiguolei as a code owner January 8, 2026 14:46
@hello-stephen
Copy link
Contributor

hello-stephen commented Jan 8, 2026

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?

@morningman
Copy link
Contributor Author

morningman commented Jan 8, 2026

run buildall

1 similar comment
@morningman
Copy link
Contributor Author

morningman commented Jan 9, 2026

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Jan 9, 2026

FE UT Coverage Report

Increment line coverage 16.67% (12/72) 🎉
Increment coverage report
Complete coverage report

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

Reviewers

@yiguolei yiguolei Awaiting requested review from yiguolei yiguolei is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@morningman @hello-stephen