Resolve missing associations for when verification fields are stored in a separate table
#Problem When using SSF to replicate datatypes, we sometimes use a separate table to store verification information, from the table represented by the replicable model.
We gather objects to be replicated and verified using the association between these two tables.
But this new verification details' table is introduced much later and not all rows from the replicable model have an associated row in the verification details' table.
As a result, the older objects don't get verified.
Discussions
The problem was diagnosed here.
#Proposed solutions This MR !66479 (closed) is a first attempt at exploring different ways to resolve the problem.
We have 2 proposed solutions:
-
Alter the verification queries to include rows with missing details' association. As mentioned in the MR above, this is a much more complex solution with chances of increasing complexity down the line.
-
Backfill verifications details' tables to create all missing records
-
Add verification details to the model's table itself. This will greatly simplify the approach and make the use of SSF uniform.
But it's affect on the table size needs to be researched.
Things to do
-
Add the new columns on a db clone and check if table size change is low enough. Ask the database team for help. -
If we can go ahead with this solution, apply the approach to all the replicables that have a separate verification details' table -
If we can't, consider option 1 or 2.
-