-
Type: Bug
-
Status: Resolved
-
Priority: Blocker
-
Resolution: Fixed
-
Affects Version/s: 2021.8
-
Component/s: Directory
-
Release Notes Summary:MongoDB indexes creation takes correctly into account the schema prefix when not defined
-
Tags:
-
Backlog priority:700
-
Sprint:nxplatform #77
-
Story Points:2
Currently indexes on (users and groups) directories are created by taking into account the schema name whereas the storage (and the queries) use the schema prefix.
As a result, we have in MongoDB :
- the data like
{ "_id": { "$oid": "61f9034b7f26b85e23903b6d" }, "description": "Group of users with read access rights", "grouplabel": "Members group", "groupname": "members" } 
- the index with the name group:groupname_1
So the index "group:groupname_1" is never used and the queries on this field could be extremely slow
Expected behavior: with the default "group" schema definition, the index name should be groupname_1
The same issue is present at the repository level. Both cases will receive the fix.
- is related to
-
NXP-31254 Cold Storage: Document index initialization on coldstorage:beingRetrieved property
- Resolved