-
Notifications
You must be signed in to change notification settings - Fork 590
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
bug: risingwave-streaming-actor' panicked at 'mem-table operation inconsistent! #8059
Comments
Seems related to stream engine, but feel free to re-assign @chenzl25 . I may take a closer look if I have some bandwidth. |
FYI I'm also planning to write a simple shrinker after #7879 , to remove extra inserts and ddl statements. |
What does |
There is already an insert(XXX) in an operator's state, and a new insert(XXX) (same pk) comes in. It can only be either Update(XXX) or Delete(XXX), but never insert(XXX). I think this is the same as the one |
Is it reasonable to dedup this operation in the same batch? |
It seems that only CREATE MATERIALIZED VIEW stream_query AS
select t_0.* FROM
m1 AS t_0
full JOIN m1 AS t_1 ON t_0.col_0 = t_1.col_0 |
Minimal reproducible example: create table t (a int primary key);
insert into t values(null);
create materialized view v as select t1.* from t as t1 full join t as t2 on t1.a = t2.a; |
|
Just try to provide another data point, The conflicting rows(pk) are all in the form of But I didn't find full-outer join in their test cases. |
- Implements `GEN INSERTs` (#3844) - Disabled for now, as there's still outstanding bug: #8059 - Implement a basic query extractor for deterministic test logs. - Added golden test for this (hence the large diff). - Reduced `CROSS JOINs` to one, else materialized view takes a long time to run. - Reduced occurrence of expressions resulting in stream nested loop join. - Increased chance to select columns rather than scalars. - Further improvements can be done in other PR. Approved-By: fuyufjh Approved-By: lmatz Co-Authored-By: Noel Kwan <noelkwan1998@gmail.com> Co-Authored-By: Noel Kwan <47273164+kwannoel@users.noreply.github.com>
Describe the bug
No response
To Reproduce
Expected behavior
No panic
Additional context
compute-node.log
The text was updated successfully, but these errors were encountered: