Project

General

Profile

Actions

Bug #3917

closed

Archiving reports should not break on on duplicate IDs or key

Added by Nicolas CHARLES about 11 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
2
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When Rudder automatically archives reports, it does it in 3 step:
  1. copy from ruddersysevents to archivedreports
  2. delete from ruddersysevents
  3. vaccumm

If the webapp is stopped between 1 and 2, we have the archive in an invalid state, causing it to fail later as it tries to insert already existing entries into the archivedruddersysevents.

In fact, we want to be able to have the archived execution reports on an other DB, so we don't want to add transaction, but be smart about how we handle already migrated reports.


Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving againReleasedFrançois ARMANDActions
Actions

Also available in: Atom PDF