Custom non-root lucene index | Adobe Higher Education
Skip to main content
Level 3
October 16, 2015
Risolto

Custom non-root lucene index

  • October 16, 2015
  • 7 risposte
  • 1983 visualizzazioni

We're running on MongoMK SP2 + hotfix 5779.

To optimize performance we are creating custom lucene indexes on content path. So something like this:

/content/sitea/oak:index/

/content/siteb/oak:index/

We have three types of search on cq:Page: for blog posts (property blog=true), events (property event=true), tags & free text.

I thought of creating four lucene indexes per site: one fulltext, three that include the properties. Something like:

/oak:index/lucene-blog --> on type cq:Page, indexing property blog, indexing property datePublished (ordered)

/oak:index/lucene-event --> on type cq:Page, indexing property event, indexing property startDate (ordered)

/oak:index/lucene-tags --> on type cq:Page, indexing property tags, indexing property datePublished (ordered)

/oak:index/lucene-fulltext --> copied over from the base oak:index

The problem is that when I do a tag based search its using the events lucene-event index. Which doesn't have all the pages that are tagged.

What's the problem? Can I have multiple lucene indexes on the same type?

Also, would it be possible to view the index when you use MongoMK?

Many thanks,

Katrien

Questo argomento è stato chiuso alle risposte.
Migliore risposta di smacdonald2008
If docs do not help, please file a ticket. (Assuming you have not done so.)

7 risposte

smacdonald2008
Level 10
October 16, 2015
If docs do not help, please file a ticket. (Assuming you have not done so.)
smacdonald2008
Level 10
October 16, 2015
A lot of our Eng team are out this week. I will get them to look at this when they get back.      
Katrien1Autore
Level 3
October 16, 2015

Also, I've noticed that other parts of the authoring environment have become slower. Sorry for not being able to specify better. But what actually happens when you use a non-root index.

E.g., when I delete the lucene-tags index, I would have expected to use the cq:Tags index (default) for any queries only containing tags. But it doesn't. It still uses the non-root lucene-events one.

Sham_HC
Level 10
October 16, 2015

If you have path restriction then use Non root index and documented at http://jackrabbit.apache.org/oak/docs/query/lucene.html

Type can be of lucene or solr. You can't have cq:page.  Offcource you can create 4 index for your property. Based on your query it picks right one.

You can make index on mongoMk.

Katrien1Autore
Level 3
October 16, 2015
I saw this doc already including others that explain the nonroot lucene index. But none give the information I requested above. Non explain if you can have multiple lucene indexes on the same page type or how it chooses the index. I ve used the query analyzer which is how I know its picking the wrong index. SP2 gives a lot of freedom re: index but unfortunately not a lot of documentation. Have been trying to get same information from daycare too.
Katrien1Autore
Level 3
October 16, 2015

So no-one knows the answer? No-one with suggestions on how to create multiple lucene indexes or that can tell me what I am doing looks right?

smacdonald2008
Level 10
October 16, 2015
Here is the AEM docs on this subject. https://docs.adobe.com/docs/en/aem/6-0/deploy/upgrade/queries-and-indexing.html I hope they help you.