[MAGNOLIA-6591] Create search index for nested components Created: 10/Mar/16 Updated: 29/Jun/18 Resolved: 17/May/16 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 5.4.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Samuel Zihlmann | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Patch included: |
Yes
|
||||||||||||
| 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)
|
||||||||||||
| Date of First Response: | |||||||||||||
| Visible to: |
Peter Mohn
|
||||||||||||
| Description |
|
Nested components are a common way to organize content elements. But unfortunately, in default JCR indexing configuration, this structure is not supported. This recursive indexing configuration is something magnolia should provide out of the box: <aggregate primaryType="mgnl:component" recursive="true"> <include primaryType="mgnl:area">*</include> </aggregate> |
| Comments |
| Comment by Federico Grilli [ 17/May/16 ] |
|
Hello Samuel, thanks for reporting this issue and providing a patch. Cheers, Federico for the Magnolia team |