Details
-
Bug
-
Resolution: Done
-
Critical
-
3.34.0
-
2
Description
Blobs created with PostgreSQL/H2 storage blob *.properties files save blob name with a leading slash.
If a user wishes to rollback from PostgreSQL and use OrientDB again, the reconcile task will need to be used to re-constitute the blobs created while using PostgreSQL.
Problems
1. The Repair - Reconcile component database from blob store implementation for OrientDB cannot reconstitute blobs with names with leading slash character.
2. In fact when the task Integrity Check: Verify integrity between asset metadata and blob properties option is selected, then the task will soft-delete postgreSQL created blobs. When a Compact blobstore task runs in OrientDB now, these previously valid blobs will get hard-deleted and permanently lost.
Expected
Reconcile task needs to be able to reconstitute blobs created in any supported database type into any other database type. This should effectively mean it transparently handles blob-name value with and without leading slash.
Attachments
Issue Links
- is related to
-
NEXUS-31130 Reconcile component database from blob store task against Nuget hosted repo generates java.lang.IllegalArgumentException
-
- New
-
-
NEXUS-30059 documented limitations of going back to OrientDB from PostgreSQL/H2 migration are not clear enough
-
- New
-
-
NEXUS-33541 Integrity check option of Repair - Reconcile component database from blob store task may delete blobs migrated from OrientDB
-
- Closed
-
- supercedes
-
NEXUS-29789 Reconcile component database from blob store task does not restore docker assets which name starts with "/"
-
- Closed
-
-
NEXUS-30042 Reconcile component database from blob store task does not restore NPM assets which name starts with "/"
-
- Closed
-