-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Create memory table with target partitions #12905
Comments
take |
I tried to implement this in a naive way by just adding the following code:
to
But I found that doing Repartition on top of a simple Projection gets overridden by physical optimization:
PS: When I skip remove_dist_changing_operators, the behavior still looks weird. The number of partitions matches target_partitions, but the data isn’t distributed properly. There’s one partition with all the data and others are empty. @jayzhan211 Would appreciate any ideas. |
|
Unassigning, no longer working on this. |
Describe the bug
When we create table inside slt, it is created with MemoryExec (Memory table). But it seems like the partitions is always one. If we want to create table with multiple partitions, we need to create multiple table and union with them.
To Reproduce
Expected behavior
I hope we can create arbitrary partitions with setting instead of creating the test with union.
Additional context
I think batch size doesn't not change the MemoryExec too, but I'm not sure about the intended behaviour
The text was updated successfully, but these errors were encountered: