mirror of
https://github.com/google/nomulus.git
synced 2025-04-29 19:47:51 +02:00
2981c1c10c
Because we need to check if a contact history is the most recent for its underlying contact resource, the query-wipe out-repeat loop no longer works ideally due to the added overhead with the query. Instead, we refactor the logic into a Beam pipeline where the query only needs to be performed once and history entries eligible for wipe out are handled individually in their own transforms. Because history entries are otherwise immutable, we can run the pipeline in relatively relaxed repeatable read isolation level. We also do not worry about batching for performance, as we do not anticipate this operation to put a lot of strains on the particular table. |
||
|---|---|---|
| .. | ||
| builder | ||
| rollback | ||
| schema-deployer | ||
| schema-verifier | ||
| build_nomulus_for_env.sh | ||
| cloudbuild-delete.yaml | ||
| cloudbuild-deploy.yaml | ||
| cloudbuild-dev-resource.yaml | ||
| cloudbuild-kythe.yaml | ||
| cloudbuild-nomulus.yaml | ||
| cloudbuild-proxy.yaml | ||
| cloudbuild-release.yaml | ||
| cloudbuild-schema-deploy.yaml | ||
| cloudbuild-schema-verify.yaml | ||
| cloudbuild-sync.yaml | ||
| cloudbuild-tag.yaml | ||
| stage_beam_pipeline.sh | ||