Lukas Eder created JCR-3607:
-------------------------------
Summary: Allow for specifying SearchIndex
indexingConfigurationClass without explicit indexingConfiguration
Key: JCR-3607
URL: https://issues.apache.org/jira/browse/JCR-3607
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: indexing
Affects Versions: 2.7
Reporter: Lukas Eder
Priority: Minor
Currently, the indexingConfiguration parameter seems to be optional in
Jackrabbit repository and workspace configuration files. So I would expect it
to remain optional, even if I override the indexingConfigurationClass
parameter. If found some relevant documentation here:
http://wiki.apache.org/jackrabbit/Search
This documentation, however, doesn't disclose the fact that an
indexingConfiguration is always needed for indexingConfigurationClass to be
considered, which can be seen in SearchIndex:
protected IndexingConfiguration
createIndexingConfiguration(NamespaceMappings namespaceMappings) {
Element docElement = getIndexingConfigurationDOM();
if (docElement == null) {
return null;
}
Here are a couple of suggestions:
1. Short-term fix: Document this behaviour and create a warning message, when
indexingConfigurationClass is specified, but indexingConfiguration is not. This
problem should not be "swallowed"
2. Long-term fix: Allow for these two parameters to be configured independently
of one another (if that makes sense)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
