I have the same situation, now I am interested why it does not return any nodes as search results?And how could I achieve that?Because speed of traversal search that does not find any node is 1ms so it can not be compared to lucene index when lucene actually goes through content and searches nodes (...

I set property type=disabled on lucene index node under oak:index

Yes

That is exactly what I need. I am doing research on how much improvement will lucene index bring.I want to run query with traversal (and get results) and then do the same with lucene index included.So no business case, just research.

I am trying to make AEM search to search for "sonja" jacket with traversal node to see how much time it will need.I disabled lucene and cqPageLucene indexes from oak:index, but can not find any nodes when trying this query in Explain Query tool:/jcr:root/content/we-retail/us/en//element(*, cq:Page)[...

On (Adobe We Retail)[GitHub - Adobe-Marketing-Cloud/aem-sample-we-retail:    We.Retail has been archived, see instead the WKND Guide:​ ] - reference project site it said:"We.Retail is no longer supported, the WKND Guide is the replacement reference site for Adobe Experience Manager."Does anyone know...

JaideepBrar​ yes, but does that mean that on the path http://server:port/sites.html/content/we-retail/language-masters/en/products there should be no inheritance? Because I can see that these properties are disabled there as well.

I am doing some search-engines related research on Adobe Experience Manager's reference site - We Retail.I've realised that page properties on some pages (ex. http://server:port/sites.html/content/we-retail/us/en/products) are disabled like it is shown in this picture. Tried on another clean instanc...