Open arikan opened 4 years ago
Hi @jexp , I've got nearly the same issue, but the log for all relations always looks like:
org.neo4j.unsafe.batchinsert.BatchRelationship@6504a875.create Relationship: 0-[:includes]->0 Node[0,used=false,rel=-1,prop=-1,labels=Inline(0x0:[]),light,secondaryUnitId=-1] not in use
So none of the relations were recreated. I've tested it with the versions 3.5.20, 3.5.19 and even 3.5.6 whereas the result was always the same.
If the keep_node_ids
property was set to false, this might be caused by the issue fixed with this pull request (I had similar issues): https://github.com/jexp/store-utils/pull/55
I set keep_node_ids to true, all relational data in the database start and end values are 0
Did you use the most recent release?
We get a really weird behavior with store-utils (tried in release 3.5.20 and release 3.5.6). It removes all relationships --millions of them-- and reconnects all to a single node, that is the one with id 0. It basically destroys the entire graph database. This is a Neo4j 3.5.5 database.
@jexp any idea why this might be happening? Thanks!
Running store utils throws error "Maximum id limit for RELATIONSHIP_TYPE_TOKEN has been reached. Generated id 65536 is out of permitted range [0, 65535]." Then, when I set
dbms.record_format=high_limit
in neo4j.config, store-util runs ok. However, the store util processs reconnects all relationship to a single node (node id 0).What should be the right approach to deal with this problem?
Here is a view from the store-copy.log
Here is how all roads lead to node id 0: