[JCR-3693] Lucene configuration - aggregation definition : problem with include-property tag

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6
• Fix Version/s: 2.6.6
• Component/s: indexing
• Assignee: Manfred Baedke
• Reporter: Geoffroy Schneck
• Created: 15/Nov/13 13:32
• Updated: 18/Dec/19 12:44
• Resolved: 22/May/15 10:21

Description

In our example , we want to limit the properties to search on for Dam Assets on "jcr:title" metadata property.

In http://wiki.apache.org/jackrabbit/IndexingConfiguration I see aggregation can be defined at property level.

Following the example, I tried 2 different config :
1)

<aggregate primaryType="dam:Asset">
		<include>jcr:content/metadata</include>
        <include-property>jcr:content/metadata/jcr:title</include-property>
    </aggregate>

2)

<aggregate primaryType="dam:Asset">
        <include-property>jcr:content/metadata/jcr:title</include-property>
property>
    </aggregate>

and then tried the result of each performing a fulltext search like /jcr:root/content/dam/geometrixx/offices//element(,dam:Asset)[jcr:contains(., 'somevalue')]

Problem : in config 1) , if another property on the metadata node has this value , the search returns the corresponding node.
In config 2) , nothing is found even if jcr:title has the value 'somevalue'...