Bug #2895
closed
Reload an archive made before an eventlog migration lead to an error
Added by Nicolas PERRON about 12 years ago.
Updated about 12 years ago.
Category:
Web - Maintenance
Description
The archive is a great functionality but is undermine by a bug related to eventlog:
- Make an archive before an eventlog migration (fileFormat=2)
- Reload this archive after the eventlog migration (fileFormat=3)
- An error appear
- Priority changed from 1 (highest) to 3
Actually, that bug only happen on migration with update on eventlog fileformat - ok, that's all migration for now, but we should be precise.
The idea here is to pre-process events from an archive to migrate them all the way up to the current fileFormat, and then load the archive.
Of course, it will be much more complex, because we read events on demand (and so have to migrate them on the fly), and some refactoring must be done to allows archive loader to use migration services...
- Target version changed from 2.4.0~rc2 to 2.4.0~rc1
Some more narrowing: we only have to support migration from fileformat as old as "2" (because before that, we didn't have archives)
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
- Status changed from Pending technical review to Released
This seems valid, thank you Francois.
I've made some corrections in the tests to allow Jenkins to succeed on them (I don't know why it needs it thought)...
- Target version changed from 2.4.0~rc1 to 2.4.0~beta5
Also available in: Atom
PDF
Updated by 
Updated by Nicolas PERRON 
Updated by 
Updated by Jonathan CLARKE