default lucene indexes used when query by fulltext | Community
Skip to main content
pmasvidal
pmasvidal
January 18, 2024
Solved

default lucene indexes used when query by fulltext

  • January 18, 2024
  • 3 replies
  • 804 views

I have created a custom oak index for the following query:

 

path=/content/myproject/en
1_property=sling:resourceType
1_property.value=myproject/components/structure/page
2_property.operation=exists
2_property=excludePage
2_property.value=false
fulltext=%text to search for% group.1_group.type=cq:PageContent
type=cq:PageContent
group.p.and=true
group.1_group.p.or=true
orderby=@dateStory
orderby.sort=desc

 

the index contains rules for excludePage, resourceType, dateStory.

The index also defines queryPaths and includedPaths, evaluating constraints.

However, and logically after reindexing my index, this query is derived to the lucene box index.

 

The same query, but without the fulltext:


path=/content/myproject/en
1_property=sling:resourceType
1_property.value=myproject/components/structure/page
2_property.operation=exists
2_property=excludePage
2_property.value=false
group.1_group.type=cq:PageContent
type=cq:PageContent
group.p.and=true
group.1_group.p.or=true
orderby=@dateStory
orderby.sort=desc

 

does succeed, it is being used by my custom index.

How can I stop this query from being derived to the box indexes? How do I get it to use the custom index by performing a fulltext search?

Thank you very much

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 TarunKumar

Hi @pmasvidal ,

Lucene full text index only support fulltext indexing and not property index or lucene property index. So if you are creating property index or lucene property index it will not create indexing for fulltext.

If a full-text index is configured, all queries that have a full-text condition use the full-text index, no matter if there are other conditions that are indexed, and no matter if there is a path restriction.

If no full-text index is configured, then queries with full-text conditions do not work as expected.


You can also look into the below link:-
https://experienceleague.adobe.com/docs/experience-manager-65/content/implementing/deploying/deploying/queries-and-indexing.html?lang=en

Thanks
Tarun

3 replies

TarunKumar
Community Advisor
TarunKumarCommunity AdvisorAccepted solution
Community Advisor
January 18, 2024

Hi @pmasvidal ,

Lucene full text index only support fulltext indexing and not property index or lucene property index. So if you are creating property index or lucene property index it will not create indexing for fulltext.

If a full-text index is configured, all queries that have a full-text condition use the full-text index, no matter if there are other conditions that are indexed, and no matter if there is a path restriction.

If no full-text index is configured, then queries with full-text conditions do not work as expected.


You can also look into the below link:-
https://experienceleague.adobe.com/docs/experience-manager-65/content/implementing/deploying/deploying/queries-and-indexing.html?lang=en

Thanks
Tarun

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    January 18, 2024

    @pmasvidal Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

    Kautuk Sahni
    narendragandhi
    Community Advisor
    narendragandhiCommunity Advisor
    Community Advisor
    January 18, 2024

    Hi @pmasvidal ,

     

    damAssetLucene oak index is your best reference for this requirement. Can you confirm if you have included evaluatePathRestrictions set to true in your index definition. Is it possible for you to share your index definition as well ?

     

     

      Terms & ConditionsAccessibility statement

      Loading footer...