Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Using ReferenceSearch outputsLucenePropertyIndex This index is deprecated in the log

tomas1979
Level 1
Level 1

Relatively straightforward usage of ReferenceSearch causes my AEM log to be populated by the following warnings

 

org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex This index is deprecated: /oak:index/lucene; it is used for query Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where contains.... Please change the query or the index definitions.

 

Code snippet:

ReferenceSearch referenceSearch = new ReferenceSearch();
        referenceSearch.setExact(true);
        referenceSearch.setHollow(true);
        Map<String, ReferenceSearch.Info> resultMap = referenceSearch.search(resourceResolver,path);
        return !resultMap.isEmpty();

 

Is this behaviour expected? What can I do to remove the warning? Would you recommend I build my own query to look for references? My objective is to find pages that are orphaned (have no references) which I'm doing by search for all cq:Page nodes in repository and then iterating through them and triggering the search using the snippet above.

Thanks

1 Accepted Solution
PuzanovsP
Correct answer by
Community Advisor
Community Advisor

Hi Tomas,

 

Adobe Folks are aware of this warning, this has been reported to them before. As per latest this warn is being tracked in their own Jira.

 

There is nothing we can do about it right now, except ignoring it and marking it as known in your wiki.

 

Regards,

Peter

View solution in original post

1 Reply
PuzanovsP
Correct answer by
Community Advisor
Community Advisor

Hi Tomas,

 

Adobe Folks are aware of this warning, this has been reported to them before. As per latest this warn is being tracked in their own Jira.

 

There is nothing we can do about it right now, except ignoring it and marking it as known in your wiki.

 

Regards,

Peter

View solution in original post