jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Kuźniak (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-202) Add configuration options for search manager
Date Thu, 09 Nov 2006 08:28:40 GMT
    [ http://issues.apache.org/jira/browse/JCR-202?page=comments#action_12448393 ] 
Jan Kuźniak commented on JCR-202:

Yes Cédric, I find it a good idea to make this configuration as wide as possible, especially
that I can easily think of more sophisticated cases (e.g. using decision tree).

In that case, I'll add two more parameters to SearchConfiguration:
<!ATTLIST SearchConfiguration
      class CDATA #IMPLIED 
      configurationFile CDATA #IMPLIED >
first one will allow to force use of different configuration mechanism, and second one to
pass configuration file for this specific mechanism.

Although I will leave possibility to put configuration into repository.xml.


> 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


View raw message