-
Notifications
You must be signed in to change notification settings - Fork 601
datastore: add columns support #3230
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Shubham Mishra <[email protected]> Signed-off-by: Mazdak Farrokhzad <[email protected]>
fb82b01
to
b7bb652
Compare
Shubham8287
commented
Sep 8, 2025
Shubham8287
commented
Sep 8, 2025
Centril
requested changes
Sep 8, 2025
Co-authored-by: Shubham Mishra <[email protected]> Signed-off-by: Mazdak Farrokhzad <[email protected]>
08b70cf
to
813f34c
Compare
Centril
reviewed
Sep 16, 2025
78e21bf
to
7ae4f0f
Compare
Shubham8287
commented
Sep 23, 2025
Centril
reviewed
Sep 23, 2025
# Description of Changes Based on,and to fix mentioned issues on #3215 i.e - 1. Mark table for truncation after anaylyzing `TxData::inserts` too. 2. `visit_truncates` can not call `schema_for_tables` for dropped tables as schema info has been deleted from `st_*` tables. Hence, added a field in `ReplayVisitor` to cache table names. This PR decouples truncation info from delete entries, since deletion alone can’t reliably tell about truncation without extra mutations later. Can be reviewed commit wise. # Testing Testing using "Add columns" PR.
Co-authored-by: Mazdak Farrokhzad <[email protected]> Signed-off-by: Shubham Mishra <[email protected]>
Centril
approved these changes
Sep 23, 2025
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.
Some minor improvements, and then this should be ready to merge.
Co-authored-by: Mazdak Farrokhzad <[email protected]> Signed-off-by: Shubham Mishra <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Sep 23, 2025
# Description of Changes - `add_columns_to_table` api to handle `AutoMigrateStep::AddColumns` -- Look at doc comment for more Info. depends on: #3261 TODO: handle `AutoMigrateStep::DisconnectAllUsers`. # API and ABI breaking changes N/A. # Expected complexity level and risk 2? Changes are not in hotpath but a bug in migration can corrupt tables. # Testing a test to exercise the API. --------- Signed-off-by: Mazdak Farrokhzad <[email protected]> Signed-off-by: Shubham Mishra <[email protected]> Co-authored-by: Mazdak Farrokhzad <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Changes
add_columns_to_table
api to handleAutoMigrateStep::AddColumns
-- Look at doc comment for more Info.depends on: #3261
TODO: handle
AutoMigrateStep::DisconnectAllUsers
.API and ABI breaking changes
N/A.
Expected complexity level and risk
2? Changes are not in hotpath but a bug in migration can corrupt tables.
Testing
a test to exercise the API.