Open Krejtcha opened 3 years ago
This option is a left-over from another era. I would not add it anymore. Anyway I think the transactional model changed slightly in the 4.1.x Java drivers or the 4.2 server line. I think we need to wrap every index creation in a separate transaction.
Right now I am creating constraints with the Neo4j Cypher step manually and let all the Neo4j Output steps wait until all the constraints are created. Is this what you are suggesting or do you plan some improvements/extension for the plugin?
I would create the indexes in a parent job as part of the overall workflow using the Execute Cypher job entry. In the end I wouldn't let the scattered steps determine these things. I would let my graph model determine which fields should have indexes or constraints.
Thanks, I will do that.
Using:
If using the "Neo4J Output" step with the option "Create indexes?" checked. The constraints are not always created even if they do not exist in the database:
The transformation finishes, but some constraints are not created thus making the dependent steps run very slow.