| Info |
|---|
This how-to is for R4J versions starting at 4.5. R4J 4.5 has not been officially released. Want to test out R4J 4.5 BETA? Reach out to us through our service desk portal to get access. |
Background
Due to very high consumption of database storage by the R4J table AO_242870_REVISION_HISTORY, development effort has been made to optimize the storage and performance of revisions in R4J.
The significant change in data structure is introduced at R4J version 4.5. Starting with this version, the R4J revision history table no longer serves as the main table for revision transactions. The evaluation of revision data is now done with the already existing history table of Jira.
...
Remove redundant data from the tables AO_242870_REVISION_HISTORY and AO_242870_ISSUE_REVISION.
Exclude issues with entries in baselines, to retain baseline information.
Execute the cleanup as a background job which cannot be aborted once executed.
Other important things:
Once executed, the cleanup process may take several hours to finish depending on the amount of data you have.
Our baseline tests with 25 million revision data finished processing between 6 to 8 hours. The process runs in the background and you can still proceed to work in R4J. However, we suggest proper planning and scheduling execution outside business hours.
R4J 4.5 revision data is not compatible with older versions of R4J as stated in our release notes.
Summary of functions affected by revisions restructure in R4J 4.5
...