## Description > Create a new index on permission group with `defaultDomainId` + `defaultDomainType` + `deleted` +`deletedAt` in order to improve the performance of the queries which are used to find the permission groups using `defaultDomainId` and `defaultDomainType`. > Also, we are going to remove an already existing index: `permission_group_workspace_deleted_compound_index` which was used earlier, when we were still dependent on `defaultWorkspaceId` Fixes #22674 Media > A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video ## Type of change - Breaking change (fix or feature that would cause existing functionality to not work as expected) - Chore (housekeeping or task changes that don't impact user perception) ## How Has This Been Tested? > Tested locally by running the server. > Indices post the server start: ``` db.permissionGroup.getIndexes() [ { v: 2, key: { _id: 1 }, name: '_id_' }, { v: 2, key: { assignedToUserIds: 1, deleted: 1 }, name: 'permission_group_assignedUserIds_deleted_compound_index' }, { v: 2, key: { defaultDomainId: 1, defaultDomainType: 1, deleted: 1, deletedAt: 1 }, name: 'permission_group_domainId_domainType_deleted_deleted_compound_index' } ] ``` ### Test Plan > Add Testsmith test cases links that relate to this PR ### Issues raised during DP testing > Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR) ## Checklist: ### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag ### QA activity: - [ ] Test plan has been approved by relevant developers - [ ] Test plan has been peer reviewed by QA - [ ] Cypress test cases have been added and approved by either SDET or manual QA - [ ] Organized project review call with relevant stakeholders after Round 1/2 of QA - [ ] Added Test Plan Approved label after reveiwing all Cypress test Co-authored-by: Nilesh Sarupriya <20905988+nsarupr@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| .run | ||
| appsmith-git | ||
| appsmith-interfaces | ||
| appsmith-plugins | ||
| appsmith-server | ||
| envs | ||
| mongo-seed | ||
| reactive-caching | ||
| scripts | ||
| .gitignore | ||
| build.sh | ||
| buildpack-run.sh | ||
| docker-compose.yml | ||
| Dockerfile | ||
| entrypoint.sh | ||
| pom.xml | ||
| Procfile | ||
| README.md | ||
| system.properties | ||
Appsmith Server
This is the server-side repository for the Appsmith framework.
For details on setting up your development machine, please refer to this Setup Guide.