jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Klimetschek <aklim...@adobe.com>
Subject Re: Indexing configuration
Date Mon, 23 Dec 2013 07:44:45 GMT
On 19.12.2013, at 23:31, anjan <polisettya@gmail.com> wrote:

> <aggregate primaryType="nt:file">
>        <include>jcr:content</include>
> </aggregate>
...
> 
> select * from [nt:file] as t where contains(t.*,'*admin*').
> 
> Is there anyway to not include this property in the index?  Any suggestions.

You are querying properties directly - the "t.*" in your contains means "all properties of
node t". This does a full text search in whatever properties are in the file nodes, including
- as mentioned - something like "jcr:lastModifiedBy" containing "admin".

The above <aggregate> index configuration however is for the node scope full text index
(aka per-node-aggregate), which you address by "." (the node) in contains/jcr:contains:

    select * from [nt:file] as t where contains(.,'admin')

(Note that wildcards such as "*admin*" aren't normally required, unless you are searching
for partial words).

[0] http://www.day.com/specs/jcr/1.0/8.5.4.5_CONTAINS.html

HTH,
Alex
Mime
View raw message