Yes.
In your jackrabbit-*.xml files you can add to the SearchIndex element the
property indexingConfiguration pointing to a xml file which holds the
jackrabbit indexing configuration. If you want a property not to be indexed
you can use:
<index-rule nodeType="nt:hierarchyNode">
<property nodeScopeIndex="false"
useInExcerpt="false">myCustomNodeData</property>
</index-rule>
Manuel
2010/5/31 Matteo Pelucco <[email protected]>
>
> Hi all,
> I'm looking to find a solution to this problem:
>
> We have few page node datas that contains extra infos about content, think
> about it as a kind of meta data.
> We noticed that the content of that node datas is searchable and it is
> visible from a standard STK Search Model.
>
> This is of course because the query pattern is
>
> private static final String SEARCH_QUERY_PATTERN = "select * from nt:base
> where jcr:path like ''{0}/%'' and contains(*, ''{1}'') order by jcr:path";
>
> @see -->>> contains(*, <<<--
>
> There is a way, using Jackrabbit, to avoid it?
>
> For example,
>
> SELECT * FROM nt:base WHERE .. AND CONTAINS(.-myCustomNodeData,
> 'fullTextSearch')
>
> But I know, it is not supported..
>
> Reading around jackrabbit & jcr I saw that for each node a customized
> search index aggregation can be set, made up with custom node datas. Can it
> be a solution?
>
> Does anybody have experience with this issue?
>
> Thansk for any advice..
> Matteo
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
>
>
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
