Evaluate user's options to avoid cyclic domain queries

[meistermeier]

I am not yet sure where this will lead to.
Something like a "Trust me, there is no cyclic data in my graph"-Option 😃
Be it an annotation, something programatically from the Neo4jTemplate side or ??.

Got the use-case multiple times now that a modelled cyclic domain is from a user side not intended to get queried as such but the underlying data forms a acyclic graph.

Of course this scenario also considers that the user has to be made much aware that relationships that might form the cycle will get deleted after loading and saving operations because they were just not fetched.

[meistermeier]

Unfortunately there is no way to determine the cycle-less number of relationships in the graph upfront reliable without sacrificing performance due to interactions (network round-trips, calculation) upfront the actual retrieval.
Also, the resulting directed query with nested "maps" to fetch a graph with a virtual 10 (random guess) hops limit is not really performant anymore.
As a result, this issue will move now the focus on evaluating how to optimise the queries issued to reduce the number of round-trips needed.