jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3693) Lucene configuration - aggregation definition : problem with include-property tag
Date Tue, 26 Nov 2013 10:26:35 GMT

     [ https://issues.apache.org/jira/browse/JCR-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alex Parvulescu updated JCR-3693:

    Attachment: JCR-36963.patch

as a follow-up the mentioned field appears to transfer properly to the parent node under the
PROPERTIES field. the reason we're not seeing the value in the logs is that the  SingletonTokenStream
simply doesn't output anything (adding a toString fixes this).

So I now think the problem comes from the fact that this aggregated field doesn't contribute
the string value to the FULLTEXT field which is used in the case of a 'contains' full-text
I'm attaching a patch with a test to demo this issue.
The provided fix would append the value of the field (only if it's a 'string' property type)
to the FULLTEXT field of the parent thus making the full-text query work.

> 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
>         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(.,
> 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

View raw message