You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/05/22 08:54:19 UTC
[jira] [Commented] (JCR-3693) Lucene configuration - aggregation
definition : problem with include-property tag
[ https://issues.apache.org/jira/browse/JCR-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555692#comment-14555692 ]
Julian Reschke commented on JCR-3693:
-------------------------------------
[~baedke] is this fixed everywhere where needed?
> 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.6, 2.7
> Reporter: Geoffroy Schneck
> Assignee: Manfred Baedke
> Fix For: 2.6.6
>
> Attachments: JCR-36963.patch
>
>
> 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.3.4#6332)