Details
-
Story
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Duplicate
-
None
-
None
Description
This issue is for automating the manual migration task.
When saving or updating an instance publicationPeriod gets initialized with the values from the dateOfPublication fields of the publication array of the instance (MODINVSTOR-724).
When migrating mod-inventory-storage to a version from the range 21.0.0 to 21.0.6 the publicationPeriod of all existing instances got automatically populated during the migration (MODINVSTOR-724). This took several hours (5 hours, or 36 hours) if there are millions of instances to migrate (MODINVSTOR-774). This is too long because the system is down and cannot been used during migration. Therefore this time consuming migration has been disabled for mod-inventory-storage >= 21.0.7 (MODINVSTOR-806).
SysOps can manually run an SQL script to migrate existing instances:
This issue is for automating this manual task. Goal is to run the migration without blocking the system, when a chunk of instances (for example 1000 instances) is migrated all other instances can still be used and edited.
Open question: Is there a need for automating the migration or can SysOps adopt the migration script and share how they manually migrate?
TestRail: Results
Attachments
Issue Links
- relates to
-
MODINVSTOR-724 Populate publication year field based on dateOfPublication field
-
- Closed
-
-
MODINVSTOR-774 Juniper migration is unreasonably slow
-
- Closed
-
-
MODINVSTOR-806 Remove instance publication period defaulting
-
- Closed
-
-
MODINVSTOR-812 Improve ways to populate publicationPeriod field
-
- Closed
-