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

Jukka Zitting commented on JCR-1201:
------------------------------------

> Could you elaborate a little on which part is architecturally unsound?

It would be good (at least with the current configuration mechanism) if all the configuration information was available already when a repository is being started, not after the startup. Otherwise you'll have a circular dependency between the repository and its configuration.

Also, I'm concerned about the implications of reconfiguring existing workspaces. Something like CREATE INDEX and its implications in SQL are relatively easy to understand, but having similar effects triggered by normal content modifications.

What's your main use case; are your more interested in being able to dynamically reconfigure things, or just in deploying the configuration in a war without having to put the configuration in an external file? In the former case I think we need to carefully consider the implications, but the latter case is much easier to solve. We could either merge indexing configuration to the normal repository configuration file, or use a relative reference and load the configuration from the classpath if that's where the repository configuration came from.

Of course, in the long run I think we should go for a more general dependency injection model for managing Jackrabbit configuration. This way you could dynamically inject whatever sort of indexing behaviour you like, even one that does read the repository for the configuration.

> 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: jackrabbit-core
>    Affects Versions: 1.3.3
>            Reporter: Ard Schrijvers
>            Priority: Minor
>             Fix For: 1.4
>
>
> 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.