Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 3.33.1
-
Fix Version/s: 3.36.0
-
Component/s: Database Migrator
-
Labels:
-
Story Points:5
-
Epic Link:
-
Sprint:NXRM Sentinels Sprint 17, NXRM Sentinels Sprint 18
-
Notability:n/a
Description
It is expected that if OrientDB is not in a healthy state prior to attempting to migrate data from it to either Postgres or H2, then the migration will either fail outright or possibly not migrate some data correctly.
Expected
As part of the migration process Sonatype defines to move OrientDB data to either Postgres or H2, add a product feature that will check for, and report any existing detected OrientDB corruption, before attempting to migrate data into the new DB. Focus should be on the component and asset classes
Attachments
Issue Links
- relates
-
NEXUS-31075 detect and repair common OrientDB data issues as part of PostgreSQL/H2 migration
-
- New
-