mirror of
https://github.com/google/nomulus
synced 2026-09-20 06:54:43 +00:00
Refactor contact history PII wipeout logic into a Beam pipeline (#1994)
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.
This commit is contained in:
@@ -97,7 +97,9 @@ steps:
|
||||
google.registry.beam.rde.RdePipeline \
|
||||
google/registry/beam/rde_pipeline_metadata.json \
|
||||
google.registry.beam.resave.ResaveAllEppResourcesPipeline \
|
||||
google/registry/beam/resave_all_epp_resources_pipeline_metadata.json
|
||||
google/registry/beam/resave_all_epp_resources_pipeline_metadata.json \
|
||||
google.registry.beam.wipeout.WipeOutContactHistoryPiiPipeline \
|
||||
google/registry/beam/wipe_out_contact_history_pii_pipeline_metadata.json
|
||||
# Tentatively build and publish Cloud SQL schema jar here, before schema release
|
||||
# process is finalized. Also publish nomulus:core jars that are needed for
|
||||
# server/schema compatibility tests.
|
||||
|
||||
Reference in New Issue
Block a user