You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2007/04/20 10:27:15 UTC

[jira] Commented: (JCR-202) Add configuration options for search manager

    [ https://issues.apache.org/jira/browse/JCR-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490263 ] 

Marcel Reutegger commented on JCR-202:
--------------------------------------

There are a couple of issues with the proposed patch:

- The configuration is query handler dependent and should therefore not be prescribed in the repository.xml. The configuration should rather be added as a separate XML file.
- Completely excluding certain nodes from indexing can have severe side effects because the index depends on each node being indexed to resolve the node hierarchy.
- Matches of property names do not respect the namespace URI
- The class NodeStateLocationAware extends from NodeState and adds the path as a fixed value, the path should rather be retrieved from a hierarchy manager.

> Add configuration options for search manager
> --------------------------------------------
>
>                 Key: JCR-202
>                 URL: https://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
>         Attachments: indexConfigurationPatch.zip
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.