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.

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

cn panic when join a mv has a order by clause #12299

Closed
ly9chee opened this issue Sep 14, 2023 · 0 comments · Fixed by #12314
Closed

cn panic when join a mv has a order by clause #12299

ly9chee opened this issue Sep 14, 2023 · 0 comments · Fixed by #12314
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@ly9chee
Copy link
Contributor

ly9chee commented Sep 14, 2023

Describe the bug

as the title said

Error message/log

compute-node-0  | thread 'risingwave-streaming-actor' panicked at 'schema check failed on BackfillExecutor: column type mismatched at position 1: expected Some(Int64), found None', src/stream/src/executor/wrapper/schema_check.rs:48:29

To Reproduce

create table t1(
  id bigint primary key,
  i bigint
);

create materialized view mv1 as
select id, i from t1 order by id, i;

insert into t1 values(1, 1);

create table t2(
   id bigint primary key
);

insert into t2 values(1);

-- the following will yield a panic
create materialized view mv2 as
select
  mv1.id as id1,
  t2.id as id2
from t2 inner join mv1 on t2.id = mv1.id;

Expected behavior

No response

How did you deploy RisingWave?

docker compose

The version of RisingWave

PostgreSQL 9.5-RisingWave-1.2.0 (0f94fdf8846a09d16f2856b816cdd9b1805a1f50)

Additional context

No response

@ly9chee ly9chee added the type/bug Something isn't working label Sep 14, 2023
@github-actions github-actions bot added this to the release-1.3 milestone Sep 14, 2023
@st1page st1page self-assigned this Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants