Skip to content

Conversation

@Jibing-Li
Copy link
Contributor

@Jibing-Li Jibing-Li commented Nov 28, 2024

What problem does this PR solve?

Previously, when using Iceberg to create MTMV, it was not possible to perceive changes in partition lists and data, so only refresh materialized view mv1 complete could be used to force full refresh.

This PR obtains the partition list of Iceberg, the last update time of the partition, and the latest snapshotId of the table.

Therefore, MTMV can be partition based on Iceberg tables and perceive changes in data, automatically refreshing partitions

For now, we only support single partition column table and the partition transform must one of hour, day, month or year.
Will support Identity transform soon.

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@doris-robot
Copy link

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?

@Jibing-Li Jibing-Li force-pushed the iceberg branch 3 times, most recently from 870c5ab to ea79a6a Compare November 28, 2024 09:16
@Jibing-Li Jibing-Li marked this pull request as ready for review November 28, 2024 09:17
@Jibing-Li
Copy link
Contributor Author

run buildall

@Jibing-Li Jibing-Li force-pushed the iceberg branch 10 times, most recently from 235a77f to 7ef6b3a Compare December 6, 2024 06:08
@Jibing-Li
Copy link
Contributor Author

run buildall

@Jibing-Li Jibing-Li force-pushed the iceberg branch 4 times, most recently from 708edf0 to 1df4979 Compare December 10, 2024 08:28
@Jibing-Li
Copy link
Contributor Author

run buildall

Copy link
Contributor

@zddr zddr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions
Copy link
Contributor

PR approved by anyone and no changes requested.

@Jibing-Li
Copy link
Contributor Author

run p0

@Jibing-Li
Copy link
Contributor Author

run buildall

@github-actions
Copy link
Contributor

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

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 16, 2024
@Jibing-Li Jibing-Li merged commit f49e609 into apache:master Dec 16, 2024
32 of 35 checks passed
github-actions bot pushed a commit that referenced this pull request Dec 16, 2024
### What problem does this PR solve?

Previously, when using Iceberg to create MTMV, it was not possible to
perceive changes in partition lists and data, so only ```refresh
materialized view mv1 complete ```could be used to force full refresh.

This PR obtains the partition list of Iceberg, the last update time of
the partition, and the latest snapshotId of the table.

Therefore, MTMV can be partition based on Iceberg tables and perceive
changes in data, automatically refreshing partitions

For now, we only support single partition column table and the partition
transform must one of hour, day, month or year.
Will support Identity transform soon.

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

### Release note

None
github-actions bot pushed a commit that referenced this pull request Dec 16, 2024
### What problem does this PR solve?

Previously, when using Iceberg to create MTMV, it was not possible to
perceive changes in partition lists and data, so only ```refresh
materialized view mv1 complete ```could be used to force full refresh.

This PR obtains the partition list of Iceberg, the last update time of
the partition, and the latest snapshotId of the table.

Therefore, MTMV can be partition based on Iceberg tables and perceive
changes in data, automatically refreshing partitions

For now, we only support single partition column table and the partition
transform must one of hour, day, month or year.
Will support Identity transform soon.

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

### Release note

None
@Jibing-Li Jibing-Li deleted the iceberg branch December 16, 2024 08:31
zddr pushed a commit to zddr/incubator-doris that referenced this pull request Jun 19, 2025
### What problem does this PR solve?

Previously, when using Iceberg to create MTMV, it was not possible to
perceive changes in partition lists and data, so only ```refresh
materialized view mv1 complete ```could be used to force full refresh.

This PR obtains the partition list of Iceberg, the last update time of
the partition, and the latest snapshotId of the table.

Therefore, MTMV can be partition based on Iceberg tables and perceive
changes in data, automatically refreshing partitions

For now, we only support single partition column table and the partition
transform must one of hour, day, month or year.
Will support Identity transform soon.

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

### Release note

None
zddr pushed a commit to zddr/incubator-doris that referenced this pull request Jun 19, 2025
Previously, when using Iceberg to create MTMV, it was not possible to
perceive changes in partition lists and data, so only ```refresh
materialized view mv1 complete ```could be used to force full refresh.

This PR obtains the partition list of Iceberg, the last update time of
the partition, and the latest snapshotId of the table.

Therefore, MTMV can be partition based on Iceberg tables and perceive
changes in data, automatically refreshing partitions

For now, we only support single partition column table and the partition
transform must one of hour, day, month or year.
Will support Identity transform soon.

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

None
morrySnow pushed a commit that referenced this pull request Jun 23, 2025
Cherry-pick from
#43959
#44419
#44415
#44567
#44673
#44998
#45273
#44911
#44726
#45652
#45659
#46257
#46641
#47026
#47166
#48172
#49956
#50979

---------

Co-authored-by: James <lijibing@selectdb.com>
Co-authored-by: Tiewei Fang <fangtiewei@selectdb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. dev/3.1.0-merged reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants