OOTB Lucene Search searching for jcr:Created (OOTB) properties

[Sb2512]

Hi All,

We are using full Text OOTB search .

When when i typring 50 in my Search Result,then it is also showing the results where jcr:created property is having "50" in the property.

How to exclude these OOTB properties from getting Searched.

Any suggestions.

[krati_garg]

Hi @Sb2512 

Please explore the backend query which is being executed as OOTB Search. It also depends on the Content you are querying. If OOTB search is on Assets, it includes popular metadata fields in its Full Text Search 

https://experienceleague.adobe.com/docs/experience-manager-64/assets/using/search-assets.html?lang=e...

And for Sites, there are fewer fields:

Not sure, how it has been zeroed down that your search results are coming from jcr:created property. Have you explored other OOTB Search Fields for both Sites and Assets?

For excluding fields from OOTB Search, you will have to define them in the Lucene Index
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/excluding-properties-from-...

[Sb2512]

Here in the search query i searched for 2023,it searched for that as it is there in jcr:created node.

I need to restrict these types of searches from my query.

[DPrakashRaj]

Similar question was answered on https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/excluding-properties-from-...

[krati_garg]

@Sb2512 Please modify cqPageLucene Index to exclude certain properties from Full Text Search. Explained over the link I shared above:

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/excluding-properties-from-...

[DPrakashRaj]

Doesn’t changing the ootb index will have negative impact. If it’s really need to update the indexing best you can do is to create your own custom index