Uploaded image for project: 'Magnolia DAM Module'
  1. Magnolia DAM Module
  2. MGNLDAM-1016

JcrAssetProvider querybuilder performance issues.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 3.0.16
    • 3.0.14
    • None

    Description

      After some more testing of our Magnolia 6 instance it was discovered that the asset chooser search options use a querybuilder built into JcrAssetProvider that suffers from similar performance issues as the JcrQueryBuilder (MAGNOLIA-8347).

      It also uses non-index queries with a like with wildcards on both ends. Which results in very slow queries.

      Also why does this not use the JcrQueryBuilder ?, there is a large overlap in the code with that.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                lam.nguyen Lam Nguyen Bao
                rico.jansen Rico Jansen
                Mathijn Elhorst, Michiel Meeuwissen, Tim Molenaar
                AuthorX
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD

                    Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Remaining Estimate - 0d
                      0d
                      Logged:
                      Time Spent - 7d 1.75h
                      7d 1.75h