-
Notifications
You must be signed in to change notification settings - Fork 526
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
refactor(lookup): use state table for lookup #3570
Conversation
let arrangement_order_types = arrangement_order_rules | ||
.iter() | ||
.map(|x| x.order_type) | ||
.collect(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This arrangement_order_types do not includes pk but only sort key. This semantics is different from Materialize executor. I investigate and found that it's because we use arrange_key here:
Materialize use directly arrangement order types in tableinfo.
Because future state table catalog may comes from frontend, I keep it unchanged in this PR.
aea0038
to
cdf3127
Compare
// The key is truncated in `arrange_keyspace` so there's no vnode to decode | ||
// TODO: refactor lookup with cell-based table and remove `deserialize_with_vnode` | ||
for (pk_with_cell_id, cell) in all_cells { | ||
tracing::trace!(target: "events::stream::lookup::scan", "{:?} => {:?}", pk_with_cell_id, cell); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the tracing cuz I think it will include too much noise?
ffaa3d6
to
8df50b0
Compare
Codecov Report
@@ Coverage Diff @@
## main #3570 +/- ##
==========================================
- Coverage 74.30% 74.29% -0.01%
==========================================
Files 773 773
Lines 109438 109424 -14
==========================================
- Hits 81321 81300 -21
- Misses 28117 28124 +7
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
8df50b0
to
8e48509
Compare
Surprised to see so little changes are okay to get this migration done 🤣 |
... except that some wrong information in my code docs might have slowed down the process 😇 |
8e48509
to
f6101c7
Compare
I may open some refactor to make some semantics more clear, e.g. #3570 (comment). |
Please use merge queue to auto-merge. Add can-merge tag. |
f6101c7
to
f3abac1
Compare
* refactor: use state table for lookup * clean * fix clone
* refactor: use state table for lookup * clean * fix clone
I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
As title.
Checklist
./risedev check
(or alias,./risedev c
)Refer to a related PR or issue link (optional)