-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
-
Empty show more show less
-
Yes
-
Yes
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:
- 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
- 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.
Acceptance criteria
- depends upon
-
MAGNOLIA-9264 Provide a foundation to manage user profiles
- Closed
- is cloned by
-
ADMINCTR-528 CLONE - Re-structure profiles workspace and disable indexing
- Closed
- relates to
-
MGNLSSO-322 Flat structure of profiles can lead to indexing issues
- Closed