Fulltext search

[adilyataim · Accepted solution]

Hi @Balamani_KK , not whole page content hierarchy is being indexed. It depends on the aggregates configuration in the Lucene index for cqage node types. You can check the default or your custom cqPageLucene index configuration and check till what level down the hierarchy nodes are being included in the index. 

Below if the default cqPageLucene index in AEM as a Cloud. In order to include more nodes you will need to create a custom Lucene index.

[Balamani_KK]

Hi im trying to use aem fulltext as 

path=/content

type=cqage

fulltext=word

 This is not giving me results, if the word is present in rich text. 

Will fulltext doesn't search in richtext? 

[adilyataim · Accepted solution]

Hi @Balamani_KK , not whole page content hierarchy is being indexed. It depends on the aggregates configuration in the Lucene index for cqage node types. You can check the default or your custom cqPageLucene index configuration and check till what level down the hierarchy nodes are being included in the index. 

Below if the default cqPageLucene index in AEM as a Cloud. In order to include more nodes you will need to create a custom Lucene index.

[Kamal_Kishor]

@Balamani_KK : Remove type filter from your query and it would work.

path=/content
fulltext=word

With type=cqage filter, it performs the search at jcr:content node level of your pages which contains all of your page level information. To test this, you can create any random property with this value and try searching, it should return the result then. I did the same and can see the results.

[DPrakashRaj]

type= cqage is not required for the full text for your use case as this property is associated with the page node only. For your use case you can use type=nt:unstructured filter for your search query

[adilyataim · Accepted solution]

Hi @Balamani_KK , not whole page content hierarchy is being indexed. It depends on the aggregates configuration in the Lucene index for cqage node types. You can check the default or your custom cqPageLucene index configuration and check till what level down the hierarchy nodes are being included in the index. 

Below if the default cqPageLucene index in AEM as a Cloud. In order to include more nodes you will need to create a custom Lucene index.

[Mahedi_Sabuj]

Hi @Balamani_KK,

You can find similar discussion here for Quick Search core component which also utilise full text search. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/quick-search-component-not...

[kautuk_sahni]

@Balamani_KK Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!