[ http://issues.apache.org/jira/browse/JCR-160?page=comments#action_12315695 ]
Marcel Reutegger commented on JCR-160: -------------------------------------- I'm currently working on integrity check which is executed on startup if the index detects a prior forced shutdown. Removing nodes from the index on the fly would be harmful to the design of the query handler. The query result shouldn't have to know about the actual index. > 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
