[MAGNOLIA-5286] Switching respectDocumentOrder to false breaks search depending on natural order Created: 30/Aug/13  Updated: 05/Dec/13  Resolved: 30/Aug/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.0
Fix Version/s: 5.1

Type: Bug Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
duplicate
is duplicated by MAGNOLIA-5301 JCR query result nodes have different... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Sprint: 5.1 Beta1- Backend

 Description   

Anything that depends on natural order of search doesn't work. For instance, in shop module where browsing product catalog is broken or
any other module/custom functionality that allows users to reorder nodes in the workbench in order to put them one after another the way users want to display them and then runs the query is broken the same way.
The reason for switching to the default value (false) for respectDocumentOrder in jackrabbit config files was more of an attempt to improve query performance when a large number of unsorted items was returned. This is actually no longer needed, as we limit the result set to the number of items being displayed and the items are usually sorted anyway.



 Comments   
Comment by Federico Grilli [ 30/Aug/13 ]

we should have an update task for this or at least update task issuing a warning for ppl to update their config manually

Generated at Mon Feb 12 04:03:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.