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 had a problem with few migrations that took more than 20 minutes each one. Those 4 migrations were modifying 150k documents each, changing the ID of each that was a GUID with CollectionName/GUID. In order to be able to do that, we needed to delete the old GUID document and insert the new CollectionName/GUID one.
The issue itself is that the migrations are correctly run in the RavenDB server but the migration record is not created and the compareExchangeLock is not removed. Also there no exception thrown in backend side
The migrations are using the PatchCollection inside the Up() giving only the RQL string for
protected Operation PatchCollection(string rql, bool waitForCompletion = true, TimeSpan? staleTimeout = null)
Am I using it incorrectly? Someone else faced this issue and was able to solve it? Our workaround is to check with queries that the migration has been correctly applied and manually delete the compareExchangeLock and add the migration record also manually
The text was updated successfully, but these errors were encountered:
Hi, I'm currently using RavenMigrations 6.0.1 in my project.
I had a problem with few migrations that took more than 20 minutes each one. Those 4 migrations were modifying 150k documents each, changing the ID of each that was a GUID with CollectionName/GUID. In order to be able to do that, we needed to delete the old GUID document and insert the new CollectionName/GUID one.
The issue itself is that the migrations are correctly run in the RavenDB server but the migration record is not created and the compareExchangeLock is not removed. Also there no exception thrown in backend side
The migrations are using the PatchCollection inside the Up() giving only the RQL string for
protected Operation PatchCollection(string rql, bool waitForCompletion = true, TimeSpan? staleTimeout = null)
Am I using it incorrectly? Someone else faced this issue and was able to solve it? Our workaround is to check with queries that the migration has been correctly applied and manually delete the compareExchangeLock and add the migration record also manually
The text was updated successfully, but these errors were encountered: