Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Boosting search indexing config

Avatar

Level 2

There's a ton of info about how to boost properties in your search index but for the life of me it seems that when i put in these boosting configs... It doesn't seem to want to index the other properties that aren't specified.  below is my indexing config that you can see where i commented the parts that i added.  My search results seem to be only based on those properties but when I take out my customization more results (just not boosted) come in as usual.  and each time i'm re-indexing the repo using http://www.wemblog.com/2011/12/how-to-rebuild-index-in-cq5-wem.html.  can anyone shed some light or offer a sample config that works for them?  thanks so much

 

<?xml version="1.0"?> <!DOCTYPE configuration SYSTEM "http://jackrabbit.apache.org/dtd/indexing-configuration-1.2.dtd"> <configuration xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:dam="http://www.day.com/dam/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:sling="http://sling.apache.org/jcr/sling/1.0"> <!-- Do not index content of subassets --> <index-rule nodeType="nt:resource" condition="ancestor::subassets/@jcr:primaryType='{http://www.jcp.org/jcr/nt/1.0}unstructured'"> </index-rule> <index-rule nodeType="nt:base"> <property nodeScopeIndex="false">analyticsProvider</property> <property nodeScopeIndex="false">analyticsSnippet</property> <property nodeScopeIndex="false">hideInNav</property> <property nodeScopeIndex="false">offTime</property> <property nodeScopeIndex="false">onTime</property> <property nodeScopeIndex="false">cq:allowedTemplates</property> <property nodeScopeIndex="false">cq:AuditEvent</property> <property nodeScopeIndex="false">cq:childrenOrder</property> <property nodeScopeIndex="false">cq:cugEnabled</property> <property nodeScopeIndex="false">cq:cugPrincipals</property> <property nodeScopeIndex="false">cq:cugRealm</property> <property nodeScopeIndex="false">cq:designPath</property> <property nodeScopeIndex="false">cq:isCancelledForChildren</property> <property nodeScopeIndex="false">cq:isDeep</property> <property nodeScopeIndex="false">cq:lastModified</property> <property nodeScopeIndex="false">cq:lastModifiedBy</property> <property nodeScopeIndex="false">cq:lastPublished</property> <property nodeScopeIndex="false">cq:lastPublishedBy</property> <property nodeScopeIndex="false">cq:lastReplicated</property> <property nodeScopeIndex="false">cq:lastReplicatedBy</property> <property nodeScopeIndex="false">cq:lastReplicationAction</property> <property nodeScopeIndex="false">cq:lastReplicationStatus</property> <property nodeScopeIndex="false">cq:lastRolledout</property> <property nodeScopeIndex="false">cq:lastRolledoutBy</property> <property nodeScopeIndex="false">cq:name</property> <property nodeScopeIndex="false">cq:parentPath</property> <property nodeScopeIndex="false">cq:segments</property> <property nodeScopeIndex="false">cq:siblingOrder</property> <property nodeScopeIndex="false">cq:template</property> <property nodeScopeIndex="false">cq:trigger</property> <property nodeScopeIndex="false">cq:versionComment</property> <property nodeScopeIndex="false">jcr:createdBy</property> <property nodeScopeIndex="false">jcr:lastModifiedBy</property> <property nodeScopeIndex="false">sling:alias</property> <property nodeScopeIndex="false">sling:resourceType</property> <property nodeScopeIndex="false">sling:vanityPath</property> <property nodeScopeIndex="false">rep:versionStorage</property> <property nodeScopeIndex="false">nt:version</property> <property nodeScopeIndex="false">nt:versionHistory</property> <!-- CUSTOM ADDED --> <property boost="5.0" useInExcerpt="false">cq:tags</property> <property boost="5.0" useInExcerpt="false">jcr:tags</property> <property boost="4.0" useInExcerpt="false">jcr:title</property> <property boost="3.0" useInExcerpt="false">navTitle</property> <property boost="3.0" useInExcerpt="false">pageTitle</property> <property boost="3.0" useInExcerpt="false">homepageTitle</property> <!-- END CUSTOM ADDED --> <property isRegexp="true">.*:.*</property> </index-rule> <!-- Cq Page for jcr:contains(jcr:content, "...") searches --> <aggregate primaryType="cq:PageContent"> <include>*</include> <include>*/*</include> <include>*/*/*</include> <include>*/*/*/*</include> </aggregate> <aggregate primaryType="dam:Asset"> <include>jcr:content</include> <include>jcr:content/metadata</include> <include>jcr:content/metadata/*</include> <include>jcr:content/renditions</include> <include>jcr:content/renditions/original</include> <include>jcr:content/renditions/original/jcr:content</include> <!-- child axis orderby index --> <include>jcr:content/renditions/original/jcr:content/jcr:lastModified</include> </aggregate> <!-- nt:file child axis orderby index --> <aggregate primaryType="nt:file"> <include>jcr:content</include> <include>jcr:content/jcr:lastModified</include> </aggregate> <!-- cq:Page child axis orderby index --> <aggregate primaryType="cq:Page"> <include>jcr:content</include> <include>jcr:content/cq:lastModified</include> </aggregate> </configuration>
1 Accepted Solution

Avatar

Correct answer by
Level 10

From your configuration you do not wish to boost the complete node but only certain properties & hence working as designed.   http://wiki.apache.org/jackrabbit/IndexingConfiguration

View solution in original post

2 Replies

Avatar

Correct answer by
Level 10

From your configuration you do not wish to boost the complete node but only certain properties & hence working as designed.   http://wiki.apache.org/jackrabbit/IndexingConfiguration

Avatar

Level 2

thanks sham for replying.  just two questions from your answer.  

1) even though i'm boosting the properties.  it still shouldn't leave out results from non-boosted properties correct?  (which i'm seeing it do)

2) How does a score of a page even work then if it's only boosting properties shouldn't these boostings aggregate to the page?  cause then i can't even see how you can weight pages with these boosted properties.  Would i have to account for every situation?  such as boost page that contains title 4, boost page with tags 4, boost page that contains both title and tags 5, etc