Slow Queries - Issue with Indexing | Community
Skip to main content
Krishna_C
Krishna_C
Level 3
December 9, 2015
Solved

Slow Queries - Issue with Indexing

  • December 9, 2015
  • 9 replies
  • 2748 views

Hi Everyone,

I have created custom lucene  index with the properties interested(most of them are custom properties created in our project) and used used cq:template as well as a property to be indexed. 

Now when I run the query indexing engine is picking up the Default Index for cq:template provided by adobe . 

So whats the priority for indexing ? Cant I use the same property in two indexes ? 

Any help is appreciated . 

Thanks,

Krishna

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 ogill

Hi Krish,

sorry I just checked and the default cq:template is a property index and not a lucene index. When you run your query, is the performance adequate with the cqtemplate property index? I take it you are searching for pages with a specific cq:template value? 

The cost is calculated for each index and the lowest cost index used.  Using the explain query tool you can see the associated costs.

Regards,

Opkar

9 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
December 9, 2015

Hi 

Please have a look at this article, i hope this would act as some help to you.

Link:- http://www.techaspect.com/blog/web-content-management/adobe-experience-manager/customizing-the-order-of-search-results

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
O
Adobe Employee
ogillAdobe Employee
Adobe Employee
December 9, 2015

Hi Krishna,

you should try and see if you can add your properties to existing OOTB indexes. From what I have heard anecdotally, try and avoid having multiple indexes for the same type, in this case you have two cq:template indexes defined. See if it helps and let us know.

Regards,

Opkar

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
December 9, 2015

kautuksahni wrote...

Hi 

Please have a look at this article, i hope this would act as some help to you.

Link:- http://www.techaspect.com/blog/web-content-management/adobe-experience-manager/customizing-the-order-of-search-results

Thanks and Regards

Kautuk Sahni

 

Kautuk,

this is an older article and does not apply to Oak index based searching.

Regards,

Opkar

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
December 9, 2015

Hi Opkar

Thank you. I will make a not for me.

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
Krishna_C
Krishna_CAuthor
Level 3
December 9, 2015

Hi Opkar,

Thanks for the information. 

I will remove the cq:template in queries and I will try to stick to custom properties , I have added this assuming that it could make my search clean. I still have to check whether I can achieve all mu use cases by removing this.

Thanks,

Krish

O
Adobe Employee
ogillAdobe EmployeeAccepted solution
Adobe Employee
December 9, 2015

Hi Krish,

sorry I just checked and the default cq:template is a property index and not a lucene index. When you run your query, is the performance adequate with the cqtemplate property index? I take it you are searching for pages with a specific cq:template value? 

The cost is calculated for each index and the lowest cost index used.  Using the explain query tool you can see the associated costs.

Regards,

Opkar

Krishna_C
Krishna_CAuthor
Level 3
December 10, 2015

Thanks Opkar. 

So the cq:template index is of the lowest cost , then I think I may have to check the indexing. This issue is happening only in one of the environments  and it is taking the correct the index in other environments. I will check the configuration again.

Thanks again :)

Krish

sureshy2015
sureshy2015
Level 4
December 10, 2015

there is a

evaluatePathRestrictions property which need to be true to pick your index + add included paths property it should be your project specific content path(this will reduce index size of yours than default).this should solve your issue

 

 

 

 

 

 

 

    
 
Krishna_C
Krishna_CAuthor
Level 3
December 10, 2015

Thanks Suresh.

I was aware of this but I was hesitant to do a code change to add paths in my queries. In 5.6 path was not indexed so we made sure our queries should not have paths within it for better performance.

As a last options I would add paths in my queries and index as well.

Thanks,

Krishna

Terms & ConditionsAccessibility statement

Loading footer...