We remove nodes from the index with index.remove(node). The index is
initialized at startup with
IndexNode index = graphDb.index().forNodes(fulltextAllNodes,
MapUtil.stringMap(provider, lucene, type, fulltext));
Removing the node from the index before executing node.delete() avoids
the
Does this problem occur with automatic node indexing?
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Does this problem occur with automatic node indexing?
We're not using auto indexing, so I can't say.
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
2011/11/17 Axel Morgner a...@morgner.de
We remove nodes from the index with index.remove(node). The index is
initialized at startup with
It cannot be only that. By the looks of it some part of your code uses
Node#hasProperty after Node#delete, which is illegal and that's what's
causing it.
It cannot be only that. By the looks of it some part of your code uses
Node#hasProperty after Node#delete, which is illegal and that's what's
causing it.
Yes, that's right. The exception is expected behaviour. But why the
node's still in the index?
I think it's just a timing problem in our
Deleting a node doesn't remove it from its indexes because there's no hard
link between a node and its indexes so it would be a costly operation. It
merely hides it from IndexHits and puts it up for deletion later
(read-repair). Are you getting the exception in another thread and/or is
that node
Using neo4j 1.4.1 we had some exceptions like
15.11.2011 18:16:11 org.structr.core.entity.AbstractNode setProperty
WARNUNG: Exception in setProperty
org.neo4j.kernel.impl.nioneo.store.InvalidRecordException: Record[22]
not in use
at
Axel,
please do, as we have found and squashed a number of potential
problems in QA for 1.5 after 1.4.1
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter
Sorry, I meant we had this with 1.4.2, but nevertheless I will
double-check 1.5 now ..
Am 16.11.2011 22:28, schrieb Peter Neubauer:
Axel,
please do, as we have found and squashed a number of potential
problems in QA for 1.5 after 1.4.1
Cheers,
/peter neubauer
GTalk: neubauer.peter
Sorry to say, but I can reproduce the behaviour with 1.5, too.
Without deleting the node from the index manually, I get still this
org.neo4j.kernel.impl.nioneo.store.InvalidRecordException:
17.11.2011 00:01:48 org.structr.core.node.TransactionCommand execute
WARNUNG: Transaction failure
Axel,
Can you isolate this into a test, and maybe send the messages.log off list
for us to look at?
On Nov 17, 2011 12:09 AM, Axel Morgner a...@morgner.de wrote:
Sorry to say, but I can reproduce the behaviour with 1.5, too.
Without deleting the node from the index manually, I get still this
11 matches
Mail list logo