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-160) Query index not in sync with workspace
Date Mon, 18 Jul 2005 12:31:10 GMT
    [ http://issues.apache.org/jira/browse/JCR-160?page=comments#action_12316031 ] 

Marcel Reutegger commented on JCR-160:
--------------------------------------

Extended consistency check to also include:
- Missing ancestor
- Unknown parent
- Nodes indexed more than once

Per default a consistency check is performced when the search index detects a prior forced
shutdown. The search index can also be configured to perform a consistency check on each startup.
Inconsistencies are repaired per default. The search index can also be configured to just
report those errors to the log.

svn revision: 219477

> Query index not in sync with workspace
> --------------------------------------
>
>          Key: JCR-160
>          URL: http://issues.apache.org/jira/browse/JCR-160
>      Project: Jackrabbit
>         Type: Bug
>   Components: query
>     Reporter: Marcel Reutegger
>     Assignee: Marcel Reutegger
>      Fix For: 1.0

>
> After some time the search index is not in sync anymore with the data in the workspace
and returns uuids which have no corresponding Node in the workspace. This results in a NodeIterator
which throws an ItemNotFoundException on nextNode().
> Instructions how to reproduce this error are not yet available.
> Possible areas for further investigation are:
> - NodeType registry which maps the node types into the workspace with the use of virtual
item states
> - versioning?
> - atomicity of indexing?

-- 
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