jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-13) Disable SearchManager
Date Tue, 26 Oct 2004 14:42:45 GMT
Disable SearchManager
---------------------

         Key: JCR-13
         URL: http://issues.apache.org/jira/browse/JCR-13
     Project: Jackrabbit
        Type: Bug
 Environment: Trunk, SVN revision 55595
    Reporter: Felix Meschberger


In previous versions (e.g. SVN tag 0.1-spec0.14) it was possible to disable the SearchManagers
by not configuring a search index path. In the current revision, a NullPointerException is
thrown, if the search index configuration is missing, tough the rest of the system would support
missing search index configuration as before.

I suggest to extend search index configuration interpretation in WorkspaceCfg.init as follows:

        Element srchConfig = wspElem.getChild(SEARCH_INDEX_ELEMENT);
        if (srchConfig != null) {
            String pathAttr = srchConfig.getAttributeValue(PATH_ATTRIB);
            if (pathAttr != null && pathAttr.length() > 0) {
                searchIndexDir = replaceVars(pathAttr, vars);
            }
        }

This only reads search index configuration if available.

The reason to switch of the SearchManager is, that in my use case enabling the SearchManager
yields a performance degradation of a factor of 10 ! Instead of taking around 500ms (which
is still too long :-) to save 3 nodes and 15 properties, it would take around 5 seconds to
save the same amount of data. And I do not need the SearchManager in my use case.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message