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
Hi,
We noticed that the collection 'roles' adds the user id to the document of its rol. But on mongo there is a max size for each document and adding every userId to that same document could cause that document arrives to that max size. The same happens in the collection 'meta' where all user ids are stored under the same document.
The text was updated successfully, but these errors were encountered:
A simple temp solution worked for us without changing the code is removing roles in the large meta document. roles in the big document is used to remove all the permissions associated to ONE resource when removing resource. ref1; ref2;
So, with this solution, the issue is we will have unnecessary permissions still in db when resource got deleted.
Hi,
We noticed that the collection 'roles' adds the user id to the document of its rol. But on mongo there is a max size for each document and adding every userId to that same document could cause that document arrives to that max size. The same happens in the collection 'meta' where all user ids are stored under the same document.
The text was updated successfully, but these errors were encountered: