[jira] Resolved: (JCR-160) Query index not in sync with workspace

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/JCR-160?page=all ]
     
Marcel Reutegger resolved JCR-160:
----------------------------------

    Resolution: Fixed

After depending issues JCR-168 and JCR-170 have been fixed, I'm now quite confident that this issue can be resolved.

If there should arise new inconsistent situations with the search index, a new issue should be created.

> 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