[
https://issues.apache.org/jira/browse/JCR-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1201:
-------------------------------
Component/s: indexing
Affects Version/s: (was: 1.3.3)
Fix Version/s: (was: 1.4)
How about an alternative approach: We make the indexing configuration a part of
the content tree by defining a new rep:index node type that contains the
relevant configuration properties. You could attach a rep:index node to any
subtree, and all nodes within that subtree would be indexed based on that
configuration.
Whenever a node is being indexed, the indexer will walk up the tree looking for
the closest ancestor with a rep:index child node. That indexing configuration
(if any) is then used to index the node. Adding, modifying, or removing a
rep:index node would trigger reindexing of the entire related subtree.
> Enable to load the indexing configuration from the repository with a config
> path like jcr:/location/in/my/workspace
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-1201
> URL: https://issues.apache.org/jira/browse/JCR-1201
> Project: Jackrabbit
> Issue Type: New Feature
> Components: indexing, jackrabbit-core
> Reporter: Ard Schrijvers
> Priority: Minor
>
> ATM, you can provide an indexing configuration file via <SearchIndex>
> configuration like
> <param name="indexingConfiguration"
> value="path-to-indexing-configuration-file"/>.
> Also see:
> 1) http://wiki.apache.org/jackrabbit/IndexingConfiguration
> 2) http://wiki.apache.org/jackrabbit/Search.
> the 'path-to-indexing-configuration-file' currently must be a file in the
> file system. Support for a indexing configuration which resides in the
> repository itself by enabling some path protocol like
> jcr://location/in/workspace in the configuration. Specifically for war
> deployment configuration files in the repository itself might be very useful.
> Perhaps adding an EventListener for instant re-configuration when the
> indexing configuration changes might be nice as well, though some (most)
> changes in the indexing configuration might require re-indexing, which would
> be bad to start automatically obviously.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
