Page MenuHomePhabricator

Investigate persisting MediaModeration timestamp in storage[16H]
Closed, ResolvedPublicSpike

Description

As a system, I would like to replace the current workflow, of using a script to find the last timestamp of when the MediaModeration purge script was run, with some sort of storage mechanism either:

    • Database
  • A database table could be created that would store a file id, timestamp and flag for a given projects uploaded images. The flag would represent whether or not the file was processed by the MediaModeration purging script. This table would be read by the purging script to determine that last processed file and the start time of the next purging sequence.
    • Flatfile
  • A text file updated each time the purging script processes a file. This file will persist/live within the MediaModeration extension and may or may not be tracked in gerrit.
    • Data Cluster
  • A text file updated each time the purging script processes a file. This file will persist/live within a data cluster, such as Hadoop,
    • Other

This will allow the MediaModeration script to run in an automated fashion.

Event Timeline

eigyan renamed this task from Investigate replacing MediaModeration timestamp with DB table [16H] to Investigate persisting MediaModeration timestamp in storage[16H].May 24 2022, 3:49 PM
mepps subscribed.

I'm closing this as it answers all the questions and is okay without product signoff.