Skip to content

Conversation

jkosh44
Copy link
Contributor

@jkosh44 jkosh44 commented Sep 12, 2023

This commit extends the catalog consistency checks by adding a consistency check for the Coordinator in-memory state. This consistency check is run as a soft-assert after catalog transactions. However, it's not run after testdrive tests, or other catalog check locations, since we don't have easy access to the Coordinator.

Motivation

This PR adds a feature that has not yet been specified.

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered.
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • This PR includes the following user-facing behavior changes:
    • There are no user-facing behavior changes.

This commit extends the catalog consistency checks by adding a
consistency check for the Coordinator in-memory state. This consistency
check is run as a soft-assert after catalog transactions. However, it's
not run after testdrive tests, or other catalog check locations, since
we don't have easy access to the Coordinator.
@jkosh44 jkosh44 closed this Sep 14, 2023
@jkosh44 jkosh44 deleted the coord-consistency-check branch September 14, 2023 14:04
andrewrodriguez-m added a commit that referenced this pull request Sep 27, 2023
Piggybacking on #21717, adding consistency checks to the coordinator
that get run in dev and during testdrive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant