-
Notifications
You must be signed in to change notification settings - Fork 762
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
Feature: Merge Into Optimizations #12595
Comments
Hello, may I help with completing this part of the development? I'm quite interested in this aspect. |
Sure, thanks. But we are in the early stage of the merge into design, it's better to wait us some time when the fundamental working is done, we may spill out some tasks, I think then is good. |
Perhaps this question may seem a bit forward, but can I also participate in the process of basic design and development for 'merge_into'? I plan to attempt an internship with Databend after completing one or two issues, so I would like to have a deeper understanding of Databend's overall design. |
@ct20000901 Feel free to take any task/issue you are interested :) |
@ct20000901 you can try this one #12901 firstly. please comment "/assign me" at #12901. |
Merge Into is supported by #12350, but it's not completed. We have many things to do.
A basic implemention :
Optimizations
hashmap(segmentId -> segment location), in src/query/sql/src/executor/physical_plans/physical_merge_into.rs' struct MergeInto, the
segments
field will hold all segments in every node, in fact every node just need to hold the info it need). (this optimization can be assigned to @JackTan25 or @SkyFan2002 )The text was updated successfully, but these errors were encountered: