You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We occasionally want to remove a span of data from the covidcast API with the following constraints:
avoid blowing away our existing estimate history for that span
avoid the API erroneously reporting 0 for that span
For the moment, we're just sacrificing the first constraint and having an admin do a DELETE FROM, but it would be less strain on the rapidly-shrinking devops team if sensor groups could do this themselves through the existing ingestion infrastructure. Maybe a magic value?
This would require the API serving routine and the metadata generator to be aware of whatever we design, so that the relevant spans are excluded.
The text was updated successfully, but these errors were encountered:
We occasionally want to remove a span of data from the covidcast API with the following constraints:
For the moment, we're just sacrificing the first constraint and having an admin do a
DELETE FROM
, but it would be less strain on the rapidly-shrinking devops team if sensor groups could do this themselves through the existing ingestion infrastructure. Maybe a magicvalue
?This would require the API serving routine and the metadata generator to be aware of whatever we design, so that the relevant spans are excluded.
The text was updated successfully, but these errors were encountered: