Implementing a Lucene Index for Internal Search
Hi,
I am using the below query to perform a full-text site search in content and another dam location which has PDFs
group.1_group.path=/content/projectname
group.1_group.type=cq:Page
group.1_group.property=jcr:content/excludeInSearch
group.1_group.property.value=false
group.1_group.property.operation=exists
group.1_group.fulltext=testcontent
group.2_group.path=/content/dam/projectname/forms
group.2_group.type=dam:Asset
group.2_group.fulltext=saa
p.limit=-1
group.p.or=true
As per suggestions from daycare, we were requested to not use any custom lucene index and add included paths to the below default indices
/oak:index/cqPageLucene
/oak:index/damAssetLucene
The indices under /oak:index/cqPageLucene/aggregates/cq:PageContent seems to have only 3 levels (i.e include0 to include2).
Hence it is missing content that is in components below the third level in the hierarchy. Modifying/adding more levels creates issues with accessing the editable templates from the authoring mode.

Can anyone please suggest what would be the best approach to create the index for this search query?