We retail - Traversal index | Community
Skip to main content
tadijam47062732
tadijam47062732
Level 3
September 23, 2019
Solved

We retail - Traversal index

  • September 23, 2019
  • 11 replies
  • 4353 views

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)[(jcr:contains(., 'sonja'))]

This is tested on We Retail project.

Why this does not find any nodes, and with indexes it does?

What will be needed for this to find pages that have "sonja" in their title? (or any other query, it is only important that I can run some query with traversal to compare its speed with lucene)

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by user05162

    Cost of traversal shows up as "Infinity" and that's the reason AEM does not start the traversal.

    Listing the costs from my local instance:

    Cost with cqPageLucene: 2799

    Cost with Lucene: 185827

    Cost with Traversal: Infinity

    I believe you should focus on COST rather than TIME as cost is directly related to time

    11 replies

    Show previous replies
    tadijam47062732
    tadijam47062732Author
    Level 3
    September 23, 2019

    It makes sense, I just thought it should run "infinity cost" if there is no cost lower than that. I will mark your question as correct. Thank you

    Terms & ConditionsAccessibility statement

    Loading footer...