AEM Search | Community
Skip to main content
bilal_ahmad
bilal_ahmad
September 9, 2019

AEM Search

  • September 9, 2019
  • 6 replies
  • 8773 views

Dear Members,

My search is fetching me relevant results but when I search for a specific page(by searching the exact page title) It shows it in the 11th position. I want to show it as my first result(if the search query matches the jcr:title or asset jcr:content/metadata/jcr:title).

Here is my xpath query :

(/jcr:root/content/mySite/sites/en-us//element(*, cq:Page)[(not(jcr:content/@isNotSearchable)) and (jcr:contains(., 'My Test Page'))] | /jcr:root/content/dam/mySite/en_us/domain//element(*, dam:Asset)[(jcr:content/metadata/@mySite:assetGated != 'yes') and (jcr:contains(., 'My Test Page'))])

I'm using AEM6.4.4.

Any input would be appreciated,

Many Thanks in Advance!

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

    6 replies

    arunpatidar
    Community Advisor
    arunpatidarCommunity Advisor
    Community Advisor
    September 9, 2019

    Hi,

    Try orderby

    JCR 1.0: 6.6.3.5 Ordering Specifier (Content Repository for Java Technology API)

    Arun Patidar
      bilal_ahmad
      bilal_ahmadAuthor
      September 9, 2019

      Thanks a lot, Arun. Much appreciate your quick response. I have tried adding order by @jcr:title but it didn't work, shows the results in the same order

      L
      Adobe Employee
      leoberliantAdobe Employee
      Adobe Employee
      September 9, 2019

      Did you try to use boost: Use Boosts | Indexing time and query runtime ?

        bilal_ahmad
        bilal_ahmadAuthor
        September 11, 2019

        Thanks a lot for the valuable suggestion. I have added boost property for jcr:title but the results appeared in the same order I

        When I add a property/node in my custom index, then it takes a lot of time to re-index. Any suggestion to make the reindexing go any quicker ? Many Thanks in advance!

        R
        rachnamehta
        September 11, 2019

        You may want to try "out-of-band" indexing

        Jackrabbit Oak – Oak Run Indexing

          H
          Adobe Employee
          Hamid1350Adobe Employee
          Adobe Employee
          September 9, 2019

          Can you verify if the same query written in SQL2 would output the results with proper ordering ? Is this isolated to XPATH ?

          bilal_ahmad
          bilal_ahmadAuthor
          September 13, 2019

          Yes, Hamid. It's fetching the results in the same order even with SQL2 query

            joerghoh
            Adobe Employee
            joerghohAdobe Employee
            Adobe Employee
            September 9, 2019

            See also Why JCR search is not suited for site search | Things on a content management system

            Jörg

              bilal_ahmad
              bilal_ahmadAuthor
              September 11, 2019

              This should be the 'must read' for any team before implementing the search for their application. thanks Jörg

              Z
              zonroc
              September 15, 2019

              I would look at using a tool like SOLR to handle searches:

              Adobe Experience Manager Help | Integrating SOLR with Adobe Experience Manager 6.4

                bilal_ahmad
                bilal_ahmadAuthor
                September 16, 2019

                Thank you so much, all for trying to help me. Apparently my segments were not proper and hence the indexes weren't getting created properly. After fixing that up, the boosting worked I was under the impression that if i'm doing a full-text search, boosting jcr:title doesn't work but that's not the case, it's working and the property is taking priority over other properties.

                  Terms & ConditionsAccessibility statement

                  Loading footer...