[MAGNOLIA-7802] Content natural order not respected in search when searching by template Created: 15/May/20 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.7.6, 6.1.5, 6.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jan Haderka | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| 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
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Support | ||||||||
| Sprint: | Maintenance 9, Maintenance 10 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
Timebox for investigation: 3 SP Content natural order not respected in search when searching by template or by any other non indexed property. To reproduce:
added screenshots to illustrate the discrepancy. |
| Comments |
| Comment by Jan Haderka [ 15/May/20 ] |
|
|
| Comment by Michael Duerig [ 27/May/20 ] |
|
I'd say this is a bug in jackrabbit. This has been reported before (apparently also in relation to Magnolia): https://issues.apache.org/jira/browse/JCR-3932 (If needed I could probably help to come up with and get a patch into Jackrabbit. ) |
| Comment by Jan Haderka [ 27/May/20 ] |
I think that if you could it would be great. Seems to be there for quite while without any attention so unless we fix it, no one else probably would. |
| Comment by Yen Lac Tue [ 27/May/20 ] |
|
Get these comments from mduerig Fixing this ourself could be possible but would be somewhat lengthy process Not sure what the situation is from the customer side. But for now I'd say there is a work around (use xpath) Fixing the bug would need to re-asses the effort (i.e. groom the bug ticket) Actual steps for fixing would be: - Develop a patch incl. test cases - Get it into Jackrabbit trunk. possibly ask for review by the Jackrabbit team - Backport to all affected Jackrabbit branches - Release all branches that received a fix (there is a process involved here which is quite heave and takes about a week) - Upgrade Magnolia to the fixed Jackrabbit version |
| Comment by Jan Haderka [ 01/Jun/20 ] |
mduerig fgrilli That is not really a workaround. The way how clients run into this is going over ${searchfn.searchPage()/searchContent() or by executing search query from template directly. But indeed as immediate remedy we should list it in known issues and mention it in documentation so that anyone searching for how to get order of templates knows not to use searchfn but instead resolve to executing jcr xpath query directly |
| Comment by Michael Duerig [ 02/Jun/20 ] |
I'll give it a shot. |
| Comment by Federico Grilli [ 02/Jun/20 ] |
|
Thanks mduerig - I guess, for the time being, a mention under known issues in doc is in order. I'll create a proper docu ticket and link it here. |
| Comment by Michael Duerig [ 03/Jun/20 ] |
|
I tried a couple of things but there seems to be no other workarounds here:
|
| Comment by Jan Haderka [ 15/Mar/21 ] |
|
The solution to this problem would require reimplementing query engine or changing repository altogether. Even newer version of JR (Oak) doesn't support natural order sorting. |