neo4j-ogm | Java Object-Graph Mapping Library for Neo4j | Graph Database library

The method needs to have a public visibility. Otherwise Spring cannot create the needed infrastructure around this (proxy related).

There is a little bit more information around this in the documentation https://docs.spring.io/spring-framework/docs/current/reference/html/data-access.html#transaction-declarative-annotations A few lines under the linked section there is a box

When you use proxies, you should apply the @Transactional annotation only to methods with public visibility. If you do annotate protected, private or package-visible methods with the @Transactional annotation, no error is raised, but the annotated method does not exhibit the configured transactional settings. If you need to annotate non-public methods, consider using AspectJ (described later).

It is possible that you are mixing the earlier neo4j-ogm with the latest Spring Data Neo4j

Check your dependencies and make sure your annotations are from the correct packages (for instance, org.springframework.data.neo4j.*)

If you follow the instructions in the link above, you should be able to resolve your errors.

Neo4j OGM 3.2 requires at least Neo4j 3.5.x (as you can see here), but you're using Neo4j 3.0.x. Note: the latest OGM version is 3.2.21.

(If you only plan to use the driver, you do not need Neo4j OGM)

Once the session is closed, you cannot access the driver's Result instance. You should instead iterate over the records while the session is open and return the result you want, something like:

Your query Match (p:Person {name: \"Person A\"}) return p just returns the person in question, not any related person. You did not even model the relationship of type KNOWS (just referring here to the wording from your question).

The person should have an additional field:

The problem is not with the query depth but with the model. The Metric entity has a relation with Calculable, but Calculable itself has no relationships defined. Spring Data cannot scan all possible implementations of the Calculable interface for their relationships. If you changed Metrics.calculates type to MutableSet, it would work as expected.

To see Cypher requests send to the server you can add logging.level.org.neo4j.ogm.drivers.bolt=DEBUG to the application.properties

Request before the change:

No, you are not doing anything wrong here and your assumption is pretty right. Neo4j-OGM caches all entities that gets loaded during a transaction / session. In the case of a findAll it collects all entities that got loaded and assigns them to their relationships. This means if it finds Sui on the second level -as you have defined the depth- of Wlisses' friends it will attach it to Fernando in the result of Tony if it is a matching relationship.

There is right now no mechanism in Neo4j-OGM to avoid this.

As documented, in order to use neo4j's Java driver, you need to specify the appropriate dependency:

Looks like this is not possible with current version. I ended up 'flatting' the conditions tree into a structure like this: