Meteor-Community-Packages/meteor-roles

forwardMigrate2 tries to drop unset index

Open

#377 opened on Aug 23, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (919 stars) (161 forks)batch import
buggood first issue

Description

While migrating to version 2 then 3, by using _forwardMigrate() then _forwardMigrate2(), an exception is raised https://github.com/Meteor-Community-Packages/meteor-roles/blob/ff9cad1db7d451a992763bfb6cd24354925f100d/roles/roles_server.js#L325

No such index is present in the user's collection

To Reproduce Start with a version 1 app. Add several roles. Use _forwardMigrate() then _forwardMigrate2() on it. The migration process stops on this exception

MongoServerError: index not found with name [roles._id_1_roles.scope_1]

Expected behavior A clean update of the servverside collections.

Environnement

  • Meteor 2.12
  • OS: OSX
  • Browser chrome, firefox

Contributor guide

Tech stack
javascriptmongodb
Domain
backenddatabase
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
MeteorMongoDBJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
First, examine the migration code in `roles server.js` around line 325 where the index drop occurs. The error indicates the index `roles. id 1 roles.scope 1` does not exist. Research should focus on understanding why the index might be missing, possibly because it was already dropped in a previous migration step. A potential fix is to check if the index exists before attempting to drop it, using `collection.indexExists()` in MongoDB. Review the migration functions ` forwardMigrate` and ` forwardMigrate2` to understand the sequence of operations and ensure indexes are only dropped when present.