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

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

Thanks for the update on the stacktrace, but it does not seem to match the current svn revision.

Are you sure you were using the latest compiled version of the DocOrderNodeIteratorImpl class?

Any chance that you can provide the node type of that node by looking up the lucene document
in the index?

Thanks a lot for your help.

> 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