cloud: feat(schema): do schema versioning and make backup non-blocking for i… #7856
Conversation
This file contains 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
…ndexing (#7852) Issue: We used to write schema/types at timestamp=1. That single bit violates the Snapshot Isolation. Hence, we couldn't run schema updates and other operations like backup concurrently. This is an issue in a multi-tenant cluster because if the backup is running we couldn't update the schema. Fix: This PR writes the schema/types at the startTs of the transaction and enables the schema updates to be made even if the backup is running. (cherry picked from commit f376a40)
github-actions
bot
added
area/schema
jarifibrahim
approved these changes
May 26, 2021
NamanJain8
added a commit
that referenced
this pull request
Jun 1, 2021
… for i… (#7856) * feat(schema): do schema versioning and make backup non-blocking for indexing (#7852) Issue: We used to write schema/types at timestamp=1. That single bit violates the Snapshot Isolation. Hence, we couldn't run schema updates and other operations like backup concurrently. This is an issue in a multi-tenant cluster because if the backup is running we couldn't update the schema. Fix: This PR writes the schema/types at the startTs of the transaction and enables the schema updates to be made even if the backup is running. (cherry picked from commit f376a40) * fix the predicate move (cherry picked from commit eb0a04b)
NamanJain8
added a commit
that referenced
this pull request
Jun 1, 2021
… for i… (#7856) * feat(schema): do schema versioning and make backup non-blocking for indexing (#7852) Issue: We used to write schema/types at timestamp=1. That single bit violates the Snapshot Isolation. Hence, we couldn't run schema updates and other operations like backup concurrently. This is an issue in a multi-tenant cluster because if the backup is running we couldn't update the schema. Fix: This PR writes the schema/types at the startTs of the transaction and enables the schema updates to be made even if the backup is running. (cherry picked from commit f376a40) * fix the predicate move (cherry picked from commit eb0a04b)
NamanJain8
added a commit
that referenced
this pull request
Jun 1, 2021
#7856) (#7873) * feat(schema): do schema versioning and make backup non-blocking for indexing (#7852) Issue: We used to write schema/types at timestamp=1. That single bit violates the Snapshot Isolation. Hence, we couldn't run schema updates and other operations like backup concurrently. This is an issue in a multi-tenant cluster because if the backup is running we couldn't update the schema. Fix: This PR writes the schema/types at the startTs of the transaction and enables the schema updates to be made even if the backup is running. (cherry picked from commit f376a40) * fix the predicate move (cherry picked from commit eb0a04b)
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.
…ndexing (#7852)
Issue:
We used to write schema/types at timestamp=1. That single bit violates the Snapshot Isolation. Hence, we couldn't run schema updates and other operations like backup concurrently. This is an issue in a multi-tenant cluster because if the backup is running we couldn't update the schema.
Fix:
This PR writes the schema/types at the startTs of the transaction and enables the schema updates to be made even if the backup is running.
(cherry picked from commit f376a40)
This change is