Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-5301

JCR query result nodes have different order than in JCR tree

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • 5.1
    • 5.0
    • core
    • None
    • Magnolia 5 with workspaces using Jackrabbit 1.5+

    Description

      When firing a JCR query, the resulting node order does not reflect the order in their JCR tree (e.g. as displayed in a content app). The reason is that Jackrabbit's attribute "respectDocumentOrder" is false by default (version 1.5+) for performance.

      Solution
      In a workspace's workspace.xml inside the SearchIndex tag, add

      <param name="respectDocumentOrder" value="true"/>
      

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                cedric Cedric Reichenbach
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD