lucene search suggestion Results issue | Adobe Higher Education
Skip to main content
P
prathapm1847112
Level 2
July 29, 2020

lucene search suggestion Results issue

  • July 29, 2020
  • 2 Antworten
  • 2152 Ansichten

Hi Experts,

 

We are using AEM 6.4.7 with Lucene Search functionality with oak indexing.  When ever the below query runs the suggestions gives results but only 255 characters even though the Description have 500 characters.

 

SELECT [rep:suggest()] FROM [nt:base] AS s WHERE suggest('Our ') AND ISDESCENDANTNODE(s, '/content/path') AND NOT [hideInSearch] = "true" .

 

 Please suggest do we need to add any config to give full sentence of the description.

 

Note: We are indexing pageTitle and Description of the page.

 

Dieses Thema wurde für Antworten geschlossen.

2 Antworten

Vijayalakshmi_S
Vijayalakshmi_S
Level 10
July 29, 2020

Hi @prathapm1847112,

Could you please let know the index used when this query is executed.

I assume it to be custom index definition. If yes, can you share the config/property details that you added specific to suggest functionality. 

    P
    prathapm1847112Autor
    Level 2
    July 29, 2020
    Hi VijayaLakshmi, I tried that solution still its giving only 255 characters.
      Vijayalakshmi_S
      Vijayalakshmi_S
      Level 10
      July 30, 2020

      Hi @prathapm1847112,

      Per Apache Jackrabbit Oak Lucene Index official documentation, there is no other config with respect to the suggestion result character limit. 

      However I surfed about this from Apache Lucene perspective which uses FST completion/ Look up for autocomplete functionality. 

      Couldn't arrive at complete flow because of the hidden implementation but found something related to constraint on Buckets. 

      Did you see any exception log something like below line 

      "Buckets must be >= 1 and <= 255:"

        SundeepKatepally
        Community Advisor
        SundeepKatepallyCommunity Advisor
        Community Advisor
        July 30, 2020

        we got similar issue , as a workaround i have switched the query from suggestion to search result query

          Allgemeine NutzungsbedingungenAccessibility statement

          Loading footer...