@gerrit.meier it seems the problem is with SDN 6 where the self reference nodes in the model generate a query that eats up the entire heap and eventually fails.
SDN 6 removed @Depth annotation and now tries to retrieve entire reachable graph in findB...
This is a problem that started coming with SDN 6. SDN 5 had @Depth annotation to limit the depth in the generated query.
I'm facing the issue and considering downgrading to SDN 5. See: java - How should one migrate from the removed @Depth annotation...
You can do that. Check the IP address of your machine where Neo4j Desktop is running. And using this IP Address and the port (default 7687) others can access the DB.
Make sure that firewall is not blocking the port.
Hi @gerrit.meier , So after struggling quite a bit with this, there are a few things I found:
It doesn't appears to be only a problem related to Component class self-referencing. OUTGOING from class and INCOMING to the other is an issue. I saw it in ...
Thank you for quick response, Gerrit! Here is the query that got generated. Please note that Component is replaced with Part here and of course there are many more relationships that are modeled.
RUN "MATCH (n:Part) WHERE n.sku = $__id__ WITH n, id(n...
