[ http://issues.apache.org/jira/browse/J
CR-257?page=comments#action_12371109 ]
Marcel Reutegger commented on JCR-257:
--------------------------------------
Paths of events that origin from the version storage are
wrong and thus are not filtered correctly anymore. This
problem was probably introduced when fixing JCR-141.
Test cases should be extended to check paths of version
events.
> Use separate index for jcr:system tree
> --------------------------------------
>
> Key: JCR-257
> URL: http://i
ssues.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.atl
assian.com/software/jira
|