Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <51893297.1143107359637.JavaMail.jira@ajax>
Date: Thu, 23 Mar 2006 09:49:19 +0000 (GMT)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-257) Use separate index for jcr:system tree
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/JCR-257?page=comments#action_12371536 ] 

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

Committed a preliminary fix. 

Most of the changes are actually located in the event system and not the search index itself. It would have probably made more sense to reopen JCR-141, but anyway...

I strongly encourage everyone to re-index an existing repository that was used with a jackrabbit svn revision between 368026 and 388123 and that is now upgraded to a higher version! Indexing of versions was completely broken between those svn revision!

I'm currently writing some additional test cases and will resolve this issue once I have commited the test cases.

> Use separate index for jcr:system tree
> --------------------------------------
>
>          Key: JCR-257
>          URL: http://issues.apache.org/jira/browse/JCR-257
>      Project: Jackrabbit
>         Type: Improvement
>     Versions: 1.0, 0.9
>     Reporter: Marcel Reutegger
>     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.atlassian.com/software/jira