[ http://issues.apache.org/jira/browse/JCR-257?page=comments#action_12370821 ]
Przemo Pakulski commented on JCR-257: ------------------------------------- I checked r386604 and it looks that doesn't work as expected. Even if 'repository wide system index that contains /jcr:system tree' is not configured, following nodes are still indexed : versionLabels, versionStorage, versionHistory, version, frozenNode. Additionally index is duplicated over all workspaces, what lead to huge index size and performance/memory problems especially if we use many workspaces. What's interesting is that if I remove all index folders, and restart repository then all indexes are rebuilded without mentioned nodes, and indexes are much smaller then. > Use separate index for jcr:system tree > -------------------------------------- > > Key: JCR-257 > URL: http://issues.apache.org/jira/browse/JCR-257 > Project: Jackrabbit > Type: Improvement > Reporter: Marcel Reutegger > 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
