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 Fri, 08 Jul 2005 11:55:12 GMT
    [ http://issues.apache.org/jira/browse/JCR-160?page=comments#action_12315295 ] 

Marcel Reutegger commented on JCR-160:

Fixing issue JCR-164 should also improve stability of the search index, because it depends
on a atomic commit of data in SharedItemStateManager.store().

Also improved NodeIterator implementation for QueryResults. The next Node instance is now
fetched ahead together with the hasNext() call. Thus it should not happen again, that after
hasNext() returned true, a call to nextNode() will throw a NoSuchElementException. The Node
that is returned may still be invalid (because it has been deleted by another session) and
throw an InvalidItemStateException when reading its state. But that may happen to any Node
instance obtained.

Committed at svn revision: 209739

> 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:
For more information on JIRA, see:

View raw message