-
Notifications
You must be signed in to change notification settings - Fork 583
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(source): remove drop_source rpc in CN #5849
Conversation
Codecov Report
@@ Coverage Diff @@
## main #5849 +/- ##
==========================================
- Coverage 75.09% 74.85% -0.25%
==========================================
Files 920 922 +2
Lines 145144 146824 +1680
==========================================
+ Hits 108996 109900 +904
- Misses 36148 36924 +776
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Co-authored-by: August <[email protected]>
Co-authored-by: August <[email protected]>
dadf001
to
50844c5
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.
Generally LGTM!
- remove TableSourceManager trait and use MemSourceManager directly. - remove useless source desc during insert_source instead.
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
@Mergifyio requeue |
☑️ This pull request is already queued |
dbaea4f
to
224f54e
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! Great job!
I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
This pr remove drop_source rpc in CN, and remove useless SourceDesc when inserting new SourceDesc.
Checklist
./risedev check
(or alias,./risedev c
)Types of user-facing changes
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)