|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
20/Mar/06 08:47 PM
|
|
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.
|
|
Description
|
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. |
Show » |
|
Improvement
Closed
Minor
REOPENED -Use separate index for jcr:system tree
JCR-257by 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.