You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Nexus 3.70.2 with the nexus-repository-composer plugin. When performing a migration to the H2 database, the composer type is not recognized. The migration completes successfully for all types except composer. Is there a way to perform the migration while preserving all composer objects?
Has anyone else encountered this issue and knows how to perform a migration from OrientDB to H2 while preserving composer objects?
The text was updated successfully, but these errors were encountered:
Migration is done offline, so no Composer plugin or similar is available. I never had a deeper look into this procedure, but I guess somebody would have to write a migration routine.
I did a dirty hacky backup+restore on my hosted repos (see #157 (comment) - use at own risk) and applied some manual metadata restore (date, uploader) afterwards. For proxy repos I’m totally fine with a reset.
As it’s a one-time process and the plugin was already way behind 3.70 my personal motivation is rather low to invest time in the old model, but it should be doable. In the end "just" some DB magic, but "someone" needs to do it.
I am using Nexus 3.70.2 with the nexus-repository-composer plugin. When performing a migration to the H2 database, the composer type is not recognized. The migration completes successfully for all types except composer. Is there a way to perform the migration while preserving all composer objects?
Has anyone else encountered this issue and knows how to perform a migration from OrientDB to H2 while preserving composer objects?
The text was updated successfully, but these errors were encountered: