justin_at_adobe wrote... Hi, This does not require reconfiguring Lucene. All you need to do is modify the Content Finder tab (/libs/wcm/extensions/contentfinder/images.js in this case). Specifically, what you would do is modify the JavaScript to add "order:jcr:content/metadata/dc:title" to the submitted query term. You can also review http://jackrabbit.apache.org/api/2.1/org/apache/jackrabbit/commons/query/GQL.html for a description of the query language used here. In some complex cases, you may...

edubey wrote... A possible solution would to do not execute this query on every page load rather you can implement your custom scheduler which will probably run every 2 hours or when loads on system is less. The task of scheduler will be store this result at some location from where content finder will pick. It will reduce your query execution as well as page load will not get affected. Hi Thanks for your idea.as per your approach, whenever dam updated with new assets i can run the scheduler/ wo...

bsloki wrote... If you are using AEM 6.x, make sure you have the relevant indexes created as oak doesnt index automatically Hi,Thanks for your reply. We are using 5.6.1. Its indexing only last modified date.

edubey wrote... Hi Michael, Please take a look @ Content Finder Query Builder : https://adobe-consulting-services.github.io/acs-aem-commons/features/contentfinder-querybuilder.html Hi Thanks for your reply.we tried with query-builder. There is a big impact on our performance side. its take much time to load a page.