You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2006/03/24 16:22:36 UTC
[jira] Resolved: (JCR-257) Use separate index for jcr:system tree
[ http://issues.apache.org/jira/browse/JCR-257?page=all ]
Marcel Reutegger resolved JCR-257:
----------------------------------
Resolution: Fixed
Assign To: Jukka Zitting (was: Marcel Reutegger)
Fixed in revision: 388559
Also added some test cases that check observation and querying on version storage.
> Use separate index for jcr:system tree
> --------------------------------------
>
> Key: JCR-257
> URL: http://issues.apache.org/jira/browse/JCR-257
> Project: Jackrabbit
> Type: Improvement
> Versions: 1.0, 0.9
> Reporter: Marcel Reutegger
> Assignee: Jukka Zitting
> Priority: Minor
>
> 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