-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
Contents in a page are found not only in the node whose primaryType is mgnl:page but also in its sub-nodes mgnl:area and mgnl:component. Adding the latter two to the JR index aggregate would allow for simpler, more accurate and possibly faster searches by simply doing e.g.
select * from [mgnl:page] as p where contains(p.*, 'foo')
rather than
select * from [nt:base] as p where contains(p.*, 'foo')
and then post-processing the results in Java by getting for each node the ancestor of type mgnl:page and finally discarding duplicates.
- is causing
-
MAGNOLIA-7231 Website specific rules for indexing affect indexing performance of all workspaces
- Closed
-
MAGNOLIA-7241 Prevent saving JCR session in versioning command
- Closed
- is depended upon by
-
MTE-19 Provide search functionality for templates
- Closed
- is related to
-
MAGNOLIA-5244 Use JR indexing configuration to fine-tune search
- Closed
-
MGNLFORUM-135 Provide search
- Closed
-
MAGNOLIA-7847 Targeted indexing configurations
- Open
-
DOCU-561 Document new features and improvements to content search in 5.4
- Closed
-
MAGNOLIA-6189 Provide highlighting option in search configuration
- Closed
- relates to
-
MAGNOLIA-6240 Add integration test for new JR's index aggregate configuration
- Open
- mentioned in
-
Page Loading...