List Info

Thread: Closed: (JCR-364) REOPENED -Use separate index for jcr:system tree




Closed: (JCR-364) REOPENED -Use separate index for jcr:system tree
user name
2006-03-20 12:48:00
     [ http://issues.apache.org/jira/browse/JCR-364?page=all ]
     
Marcel Reutegger closed JCR-364:
--------------------------------

    Fix Version:     (was: 1.0)
     Resolution: Duplicate

I'm closing this issue again and will re-open issue 257
because 1.0 is not yet released and 257 has 'Fix Version'
set to 1.0.

> REOPENED -Use separate index for jcr:system tree
> ------------------------------------------------
>
>          Key: JCR-364
>          URL: http://i
ssues.apache.org/jira/browse/JCR-364
>      Project: Jackrabbit
>         Type: Improvement
>     Reporter: Miro Walker
>     Assignee: Marcel Reutegger
>     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.atl
assian.com/software/jira

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )