[MGNLUI-25] As a user, I can search for content in nested areas and components Created: 09/Oct/12 Updated: 10/Mar/21 Resolved: 10/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | workbench |
| Affects Version/s: | 5.2 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Major |
| Reporter: | Federico Grilli | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | search | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
||||||||||||||||
| Description |
|
Background info:
The solution to the above problems is to use JR indexing configuration, in particular aggregate indexing. http://wiki.apache.org/jackrabbit/IndexingConfiguration To reproduce in demo-project:
The term we searched for is actually present in page /demo-project/about/subsection-articles/article namely in a component (named 0) found in the sub-area /extras/extras1. So, the first hit (the article page) is correct, whereas the second one (the subsection-articles page) is not. Trying with text only present in the same page in a component under the content area would instead return 3 hits!
This might possibly have to do with this JR issue https://issues.apache.org/jira/browse/JCR-2947 |