429 created a new table new_image with a modified and improved schema over the old image table. The service layer expects to ingest the image table.
Suggested Improvement
Now, having verified that new_image seems to work for all the upstream ingestion steps, we need to swap the table names around so that the service layer will attempt to ingest from the new table. The necessary swaps are:
image -> old_image
new_image -> image
This involves
swapping the names in the DB,
swapping the names in the local testing dev environment, and
modifying the parts of the codebase that deal in SQL to point at the correct tables.
Benefit
We'll finally be ingesting the new deduplicated data with the new schema into the service layer!
Alternatives
We could change the service layer to point to new_image for its ingestion, but that would be confusing (or amusing) in the future.
Why is this old table called new_image ?
-- Me, 3 years hence
Current Situation
429 created a new table
new_imagewith a modified and improved schema over the oldimagetable. The service layer expects to ingest theimagetable.Suggested Improvement
Now, having verified that
new_imageseems to work for all the upstream ingestion steps, we need to swap the table names around so that the service layer will attempt to ingest from the new table. The necessary swaps are:image -> old_imagenew_image -> imageThis involves
Benefit
We'll finally be ingesting the new deduplicated data with the new schema into the service layer!
Alternatives
We could change the service layer to point to
new_imagefor its ingestion, but that would be confusing (or amusing) in the future.