Return-Path: 
 <dev-return-38716-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 22F331062C
	for <apmail-jackrabbit-dev-archive@www.apache.org>;
 Fri, 15 Nov 2013 13:33:29 +0000 (UTC)
Received: (qmail 50300 invoked by uid 500); 15 Nov 2013 13:33:28 -0000
Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
Received: (qmail 50142 invoked by uid 500); 15 Nov 2013 13:33:23 -0000
Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:dev@jackrabbit.apache.org>
List-Id: <dev.jackrabbit.apache.org>
Reply-To: dev@jackrabbit.apache.org
Delivered-To: mailing list dev@jackrabbit.apache.org
Received: (qmail 49232 invoked by uid 99); 15 Nov 2013 13:33:21 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Nov 2013 13:33:21 +0000
Date: Fri, 15 Nov 2013 13:33:21 +0000 (UTC)
From: "Geoffroy Schneck (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12679393.1384522347639.80838.1384522401122@arcas>
In-Reply-To: <JIRA.12679393.1384522347639@arcas>
References: <JIRA.12679393.1384522347639@arcas>
Subject: [jira] [Created] (JCR-3693) Lucene configuration - aggregation
 definition : problem with include-property tag
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

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)