Skip to content
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

fix(restore): Set kv version to restoreTs for all keys (#7930) #8563

Merged
merged 1 commit into from
Feb 2, 2023

Conversation

mangalaman93
Copy link
Member

@mangalaman93 mangalaman93 commented Jan 4, 2023

The kv version should be set to restore timestamp for rolled-up keys and schema keys as well. It would be inconsistent to write data at different timestamp compared to the timestamp that we use for writing schema keys.

@CLAassistant
Copy link

CLAassistant commented Jan 4, 2023

CLA assistant check
All committers have signed the CLA.

@mangalaman93 mangalaman93 added the slash-to-main PRs which bring slash branch on par with main. label Jan 4, 2023
matthewmcneely
matthewmcneely previously approved these changes Jan 5, 2023
MichelDiz
MichelDiz previously approved these changes Jan 5, 2023
@coveralls
Copy link

coveralls commented Feb 1, 2023

Coverage Status

Coverage: 66.91% (+0.2%) from 66.733% when pulling 7f72777 on aman/restoreTs into 9739415 on main.

The kv version should be set to restore timestamp for rolled-up keys
and schema keys as well.
@mangalaman93 mangalaman93 merged commit b100a90 into main Feb 2, 2023
@mangalaman93 mangalaman93 deleted the aman/restoreTs branch February 2, 2023 05:11
all-seeing-code pushed a commit that referenced this pull request Feb 8, 2023
The kv version should be set to restore timestamp for rolled-up keys and
schema keys as well. It would be inconsistent to write data at different
timestamp compared to the timestamp that we use for writing schema keys.
all-seeing-code pushed a commit that referenced this pull request Feb 8, 2023
The kv version should be set to restore timestamp for rolled-up keys and
schema keys as well. It would be inconsistent to write data at different
timestamp compared to the timestamp that we use for writing schema keys.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
slash-to-main PRs which bring slash branch on par with main.
Development

Successfully merging this pull request may close these issues.

6 participants