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

batch: 3-node with table-v2 #311

Closed
Tracked by #56
BugenZhao opened this issue Feb 14, 2022 · 1 comment · Fixed by #334
Closed
Tracked by #56

batch: 3-node with table-v2 #311

BugenZhao opened this issue Feb 14, 2022 · 1 comment · Fixed by #334

Comments

@BugenZhao
Copy link
Member

@BugenZhao

Yesterday I have discussed with @liurenjie1024 and I thought we were going to solve the problem ("3-node olap e2e not works") in such way:

  1. Let the RowSeqScanNode run in singleton, since the parallel scan from Hummock is still under development.
  2. Let other executors in the OLAP plan run in MPP, so OLAP e2e test can still run in 3-node distributed mode

Is it possible?

Originally posted by @fuyufjh in #228 (comment)

@BugenZhao
Copy link
Member Author

BugenZhao commented Feb 14, 2022

After @wyhyhyhyh 's hard work in #200, we are able to create materialized view under multi-node configuration.

However, the Insert and RowSeqScan executors still can't work correctly since we used to design them based on a shared-nothing storage (legacy Bummock). Check #308 for more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant