-
Notifications
You must be signed in to change notification settings - Fork 206
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: introduce TableOperator
to encasulate operation of tables
#808
feat: introduce TableOperator
to encasulate operation of tables
#808
Conversation
Codecov Report
@@ Coverage Diff @@
## main #808 +/- ##
==========================================
- Coverage 67.98% 67.84% -0.14%
==========================================
Files 299 300 +1
Lines 47174 47324 +150
==========================================
+ Hits 32073 32109 +36
- Misses 15101 15215 +114
... and 2 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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
…ache#808) * add `register_table` in `Schema`, adapt this change in volatile based schema impl. * refactor table opertations. * abort the modification in meta event service. * add table operator to meta_event_service. * add table operator to local recovery. * make clippy happy. * update integration tests. * remove useless table operation methods, and schema id in related requests. * address CR.
Which issue does this PR close?
Closes #
Rationale for this change
Now, we directly call the method in
Schema
for table operations, that led to tons of dulicated codes(e.g. create and drop inmeta event service
andinterpreter
,open
inmeta event servie
andlocal recovery
).In this pr,
TableOperator
is introduced to escasulate such operations for eliminating the duplicateds.What changes are included in this PR?
TableOperator
.open table
andclose table
Schema
, and addregister_table
andunregister_table
.table_engine
for opening and closing.TableOperator
.Are there any user-facing changes?
None.
How does this change test
Test exist tests.