-
Notifications
You must be signed in to change notification settings - Fork 157
Skip relationships with missing nodes instead of failing #65
Comments
Actually it already does this for index lookups, I can add it for direct node id lookups too. |
Yes, I think it would be a nice feature. Perhaps with a warning error being Thanks! On Thu, Jan 16, 2014 at 4:45 AM, Michael Hunger [email protected]:
|
The new neo4j-import tool supports skipping and logging unmet relationships. See http://neo4j.com/docs/stable/import-tool.html http://neo4j.com/docs/stable/import-tool.html
|
@jexp Thanks. If you set --skip-bad-relationships it says they're logged up the the max indicated by --bad-tolerance. Do you know if this means the import will still continue, just no longer logging the bad ones it comes across? |
ohh, this doesn't help with batch inserting... perhaps you could queue rels with missing nodes as, let's say, RelationshipPrecalculations, and check whether the nodes are still missing at the end of the import? that would make more sense than just throwing an error immediately I think |
When either the "start" or "end" node is a relationship does not exist the import fails with:
Where 12972393 was the missing node ID.
Is it possible for a warning message to be printed and the relationship skipped instead of having the whole import fail? Even if this was not the default behavior, I think it would be a useful feature as a configuration option.
The text was updated successfully, but these errors were encountered: