[ADMINCTR-523] Re-structure profiles workspace and disable indexing Created: 18/Jan/24  Updated: 06/Feb/24

Status: In Progress
Project: Admincentral
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.37

Type: Story Priority: Neutral
Reporter: Nguyen Phung Chi Assignee: Nguyen Phung Chi
Resolution: Unresolved Votes: 0
Labels: SSO_and_Security_Initiative
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSSO-322 Flat structure of profiles can lead t... In Progress
dependency
depends upon MAGNOLIA-9264 Provide a foundation to manage user p... In Progress
Template:
Acceptance criteria:
Empty
Release notes required:
Yes
Team: AdminX
Work Started:

 Description   

Context

Source of the problem: MGNLSSO-322 found slow indexing issue

One of the biggest contributing factors to slow indexing is Too many entries in JCR at the same level.

Here for user profiles, we don't expect much more than few hundreds/thousands of entries

Proposed solution

We should do both in below:

  1. as mentioned disable indexing for the profiles workspace, afaik we never query the workspace, we only access by absolute path (worth double-checking).
    • we can do that standard, like we do forĀ imaging. Beware that this config may only apply to newly created workspaces (i.e. fresh install), we would need to add RNs for "emptying" the SearchIndex config in the existing workspace directory on the file-system, and we could start doing that in 6.3 only
  2. re-structuring the workspace, and give a proper API facade for this functionality. This enables further user preferences and "personalized" use cases, especially with projects increasingly using SSO and at a larger scale than before.

Generated at Sun Feb 11 23:07:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.