Meteor-Community-Packages/meteor-roles

forwardMigrate2 tries to drop unset index

Open

#377 建立於 2023年8月23日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)JavaScript (919 star) (161 fork)batch import
buggood first issue

描述

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

貢獻者指南

技術棧
javascriptmongodb
領域
backenddatabase
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
MeteorMongoDBJavaScript
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
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.