-
Notifications
You must be signed in to change notification settings - Fork 600
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
feat(batch): apply row-based encoding for materialize executor and batch mode #4335
Conversation
@@ -49,8 +49,8 @@ pub struct RowSeqScanExecutor<S: StateStore> { | |||
} | |||
|
|||
pub enum ScanType<S: StateStore> { | |||
TableScan(BatchDedupPkIter<S, CellBasedRowSerde>), | |||
RangeScan(StorageTableIter<S, CellBasedRowSerde>), | |||
TableScan(StorageTableIter<S, RowBasedSerde>), |
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.
Do we still need to differentiate TableScan
and RangeScan
?
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.
Not sure whether we need to differentiate, if we have row-based dudup pk. cc @BugenZhao
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.
With dedup fully implemented, they should also use the same iterator. For now I think there's no need to differentiate them.
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.
Will refactor this part in next PR.
Codecov Report
@@ Coverage Diff @@
## main #4335 +/- ##
==========================================
+ Coverage 74.42% 74.47% +0.04%
==========================================
Files 846 846
Lines 122994 123168 +174
==========================================
+ Hits 91537 91727 +190
+ Misses 31457 31441 -16
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 |
…into wcy/row_based_batch
5415e00
to
77ce7f0
Compare
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.
LGTM
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.
Good work! Thanks for the PR!
…tch mode (risingwavelabs#4335) * x * row-based mv and batch * remove redudant code * fmt happy * fmt happy * doc * remove clone * refactor * fix column_mapping * update comments Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
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
)Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.
Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)
close #4367