jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cédric Damioli (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-202) Add configuration options for search manager
Date Tue, 07 Nov 2006 14:42:54 GMT
    [ http://issues.apache.org/jira/browse/JCR-202?page=comments#action_12447809 ] 
            
Cédric Damioli commented on JCR-202:
------------------------------------

May the above rule-based suggestion be only a default implementation of the SearchConfiguration
?
IMHO with these simple XML rules, you can't cover all possibilities.

What about <SearchConfiguration class="whatever"/> ? 
Where the class is an implementation simply answering to 
boolean include (Node node);
boolean exclude (Node node);

Your proposed rule-based implementation may become the standard, default one, while enabling
more advanced needs to be also implemented.

Thoughts ?

> Add configuration options for search manager
> --------------------------------------------
>
>                 Key: JCR-202
>                 URL: http://issues.apache.org/jira/browse/JCR-202
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: config
>    Affects Versions: 0.9, 1.0, 1.0.1
>         Environment: all
>            Reporter: Michael Aemisegger
>
> Right now, if the search manager is active, everything is indexed, even the system branch
of a workspace with the versions.
> take parameters / conditions into account whether a node should be indexed:
> - path
> - node type
> - property type
> - property name
> see also http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/3343

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message