Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

device report retention changes #653

Merged
merged 4 commits into from
Feb 19, 2019
Merged

Conversation

karenetheridge
Copy link
Contributor

run all incoming reports through validations, and then possibly delete older passing reports

We do not keep a device report if it follows a passing result and also is followed by a passing
result. This means that we consider previous reports for deletion, never the most recent one.

closes #619, #461.

@karenetheridge karenetheridge added enhancement extends current functionality validation database involves database schema or config changes, or non-trivial query authoring labels Feb 12, 2019
@karenetheridge karenetheridge added this to the v2.24 milestone Feb 12, 2019
@karenetheridge karenetheridge force-pushed the ether/device_report-retention branch from e3dfdf5 to d088336 Compare February 13, 2019 19:05
perigrin
perigrin previously approved these changes Feb 19, 2019
…e older passing reports

We do not keep a device report if it follows a passing result and also is followed by a passing
result. This means that we consider *previous* reports for deletion, never the most recent one.

- remove duplicate device report detection logic (see #460, #492): we now once again process
  all device reports as they come in.
- reorder validation_status_enum for nicer queries
- create a command-line script to thin out historical reports.

closes #619, #461.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
database involves database schema or config changes, or non-trivial query authoring enhancement extends current functionality validation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Report Revision Retention Refactor
2 participants