JcrAssetProvider querybuilder performance issues. (MGNLDAM-1016)

[MGNLDAM-1025] Add new node name search configurations Created: 10/May/22  Updated: 12/May/22  Resolved: 12/May/22

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Documentation Task Priority: Neutral
Reporter: Adrian Brooks Assignee: Adrian Brooks
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Sprint: AuthX 8, AuthX 9, AuthX 10
Team: AuthorX

 Description   

Update this page: https://docs.magnolia-cms.com/product-docs/6.2/Modules/List-of-modules/Digital-Asset-Management-module/Magnolia-DAM-JCR-implementation.html#_magnolia_dam_jcr_configuration

In this ticket we made some improvements for query. BTW, We are now supporting node name search configurations
For documentation:

  • Contains: check for the existing node contains search string.
  • StartWith: check if the node name is start with search string.
  • EndWith:  check if the node name is end with search string.
  • None: ignore LocalName search (only full text search is using)


 Comments   
Comment by Adrian Brooks [ 12/May/22 ]

Merged into release branch: release/6.2.19-dev

Generated at Mon Feb 12 05:05:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.