spring-data-neo4j

I'm trying to utilize the timetree library in my spring data neo4j 4.0.0 project. As elaborated in this page, https://github.com/graphaware/neo4j-timetree , I've edited my neo4j.properties file to enable the auto event attaching, add timetree dependency to my gradle, and set a property 'creationDate' in the event node with Long data type. Albeit everything looks as it should be, it still doesn't create any timetree. Hereby is my neo4j.property file: # Runtime must be enabled like this com.graphaware.runtime.enabled=true # A Runtime module that takes care of attaching the events like this (TT

i want to store some data in my neo4j database. i use spring-data-neo4j for that. my code is like the follow: for (int i = 0; i < newRisks.size(); i++) { myRepository.save(newRisks.get(i)); System.out.println("saved " + newRisks.get(i).name); } My newRisks-array contains circa 60000 objects and 60000 edges. Every node and edge has one property. The duration of this loop is circa 15 - 20 minutes, is this normal? I used Java VisualVM to search some bottlenecks, but my average CPU usage was 10 - 25% (of 4 cores) and my heap was less than half full. There are any options to boost up this operation

I have a JPA web application with some integration tests against the JPA repositories. There are no integration tests against the Neo4J repositories yet. Now, I have added some Neo4J functionality to this existing JPA web application. I'm this now using Neo4J repositories, alongside JPA repositories. My entities and repositories are named differently and are sitting in different packages. My tests all extend the following class: @WebAppConfiguration @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(classes = { ApplicationConfiguration.class, WebSecurityTestConfiguration.class,

I have a simple setup and encountered a puzzling (at least for me) problem: I have three pojos which are related to each other: @NodeEntity public class Unit { @GraphId Long nodeId; @Indexed int type; String description; } @NodeEntity public class User { @GraphId Long nodeId; @RelatedTo(type="user", direction = Direction.INCOMING) @Fetch private Iterable<Worker> worker; @Fetch Unit currentUnit; String name; } @NodeEntity public class Worker { @GraphId Long nodeId; @Fetch User user; @Fetch Unit unit; String description; } So you have User-Worker-Unit with a "currentunit" which marks in user