Skip to content

branch-4.0: [fix](nereids)allow sync mv has same columns as base table when it has where clause #58105 #58180

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

branch-4.0: [fix](nereids)allow sync mv has same columns as base table when it has where clause #58105 #58180

wants to merge 1 commit into from
+17 −2

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Nov 20, 2025

Cherry-picked from #58105

@starocean999
[fix](nereids)allow sync mv has same columns as base table when it ha…
4945aa0 
…s where clause (#58105)

```
create table d_table(
    k1 int null,
    k2 int not null,
    k3 bigint null,
    k4 varchar(100) null
)
duplicate key (k1,k2,k3)
distributed BY hash(k1) buckets 3
properties("replication_num" = "1");

create materialized view kx1234 as select k1 as y1, k2 as y2, k3 as y3, k4 as y4 from d_table where k1 = 1;

before this pr, the create mv command will fail because the columns in the select list is same as base table. 
But the mv is useful, because it has where clause to filter some data. This pr correct it
```
@github-actions github-actions bot requested a review from yiguolei as a code owner November 20, 2025 07:33
@Thearas
Copy link
Contributor

Thearas commented Nov 20, 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?

@Thearas
Copy link
Contributor

Thearas commented Nov 20, 2025

run buildall

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

@Thearas @starocean999