[
https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676703#action_12676703
]
mreutegg edited comment on JCR-1998 at 2/25/09 8:55 AM:
----------------------------------------------------------------
> The default value would be the current behaviour (using background thread)
This is actually wrong.
The cache initialization was introduced in 1.5.0 (JCR-1337), then improved and
put into a background thread in current trunk (JCR-1884). Which means it should
be the other way around. Default is to *not* run initialization in a background
thread.
was (Author: mreutegg):
> The default value would be the current behaviour (using background thread)
This is actually wrong.
The cache initialization was introduced in 1.5.0 (JCR-1337), then improved and
put into a background thread in current trunk (JCR-1998). Which means it should
be the other way around. Default is to *not* run initialization in a background
thread.
> Initialize hierarchy cache on startup
> -------------------------------------
>
> Key: JCR-1998
> URL: https://issues.apache.org/jira/browse/JCR-1998
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Marcel Reutegger
> Priority: Minor
>
> In some cases it may be desirable to initialize the hierarchy cache in the
> search index on startup. Currently this initialization is done in the
> background. For larger workspaces, this puts considerable load on the
> repository and may slow down access and queries. There should be a
> configuration parameter that forces the repository to initialize the
> hierarchy cache on startup and only return the repository instance when the
> initialization is completed. The default value would be the current
> behaviour (using background thread).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
