jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-257) Use separate index for jcr:system tree
Date Tue, 20 Dec 2005 11:15:30 GMT
    [ http://issues.apache.org/jira/browse/JCR-257?page=comments#action_12360905 ] 

Marcel Reutegger commented on JCR-257:
--------------------------------------

Separated index as proposed. There is one repository wide system index that contains /jcr:system
tree. In addition to this 'global' index there are still the workspace indexes as before.
Queries are executed on both indexes and will return results from both indexes.

Separating the indexes now also allows to disable indexing of versions. One simply does not
configure a system index on the repository level.

Important note: this causes a minor backward compatibility issue. Existing configurations
do not have a system search index configured on the repository level and will not index versions
anymore. That means, queries will return versions of nodes that have been checked in before
this code change but no checkins after this change. Apart from that Jackrabbit will work just
fine. If you need to search versions of nodes see below how.

Migration instructions:
- add a SearchIndex element at the end of the repository configuration. See jackrabbit/src/main/config/repository.xml
for an example
- delete index folders in all your workspace directories
- restart jackrabbit (will re-index workspaces and jcr:system tree)

svn revision: 357961

> 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


Mime
View raw message