[ESRCH-41] Mitigate impact of missing Lucene index on Jackrabbit features Created: 20/Oct/20  Updated: 26/Jul/21

Status: Accepted
Project: External Enterprise Search
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Some Jackrabbit itself rely on the presence of a search index. These features degrade or fail when no search index is present. The affected features are (full details here):

  •  org.apache.jackrabbit.api.security.user.UserManager#findAuthorizables(java.lang.String, java.lang.String, int) falls back to traversal of the content hierarchy.
  • AccessControlProvider#getEffectivePolicies() throws RepositoryException
  • Weak references can't be resolved (Node#getWeakReferences()) and throw a RepositoryException

None of these feature are currently used in Magnolia.

We should either make sure that future versions of Magnolia don't inadvertently start relying on these features or provide replacement implementations for them.

 

 

 

 


Generated at Mon Feb 12 01:55:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.