You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Miro Walker (JIRA)" <ji...@apache.org> on 2006/03/20 13:16:59 UTC
[jira] Commented: (JCR-364) REOPENED -Use separate index for
jcr:system tree
[ http://issues.apache.org/jira/browse/JCR-364?page=comments#action_12371073 ]
Miro Walker commented on JCR-364:
---------------------------------
I've reopened this JCR-257 by cloning it (apologies if that's not the correct way to handle it, but I'm not that used to JIRA), based on Przemek's comment that it appears the fix does not work as expected. This is causing us problems as indexes are growing to enourmous sizes.
> REOPENED -Use separate index for jcr:system tree
> ------------------------------------------------
>
> Key: JCR-364
> URL: http://issues.apache.org/jira/browse/JCR-364
> Project: Jackrabbit
> Type: Improvement
> Reporter: Miro Walker
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.0
>
> Currently each workspace index also includes index data of repository wide data (e.g. version nodes under jcr:system). There are several drawbacks with this approach:
> - indexing is duplicated and does not scale when using a lot of workspaces
> - workspaces cannot be 'put to sleep' when they are not actively used.
> The repository should have an additional index for system data, which includes: versioning and nodetype representation in content. Basically data under /jcr:system.
> Queries issued on a workspace will then use two index to execute the query: the workspace index and the system index.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira