jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffroy Schneck (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3693) Lucene configuration - aggregation definition : problem with include-property tag
Date Fri, 15 Nov 2013 13:33:21 GMT
Geoffroy Schneck created JCR-3693:
-------------------------------------

             Summary: Lucene configuration - aggregation definition : problem with include-property
tag
                 Key: JCR-3693
                 URL: https://issues.apache.org/jira/browse/JCR-3693
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: indexing
    Affects Versions: 2.7.2
            Reporter: Geoffroy Schneck


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)
{code}<aggregate primaryType="dam:Asset">
		<include>jcr:content/metadata</include>
        <include-property>jcr:content/metadata/jcr:title</include-property>
    </aggregate>{code}
2)
{code}<aggregate primaryType="dam:Asset">
        <include-property>jcr:content/metadata/jcr:title</include-property>
property>
    </aggregate>{code}

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'...



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message