@haikal, I was able to code around the concurrency issue I was facing outside of Grakn. I think it might still be a useful feature but no rush on my part.
As for the second question, I’m asking if Grakn can expose the traversal it takes with the query. You’re saying that I should run a query, get an answer, run another query, get the final answer. I’m asking if I make a query which starts from nothing and gets me the final answer; Can I instead of getting the final answer get the traversal path which is performed by Grakn which leads to that final answer? This is different than running queries and getting answers which you then use to fuel further queries.
I think this would help with debugging and just my general understanding of what Grakn is actually doing under the cover. I know I can turn logging on but I’m struggling to understand how to follow them. If instead I could get the traversal path that Grakn performs and iterate it I could see it’s doing 50,000 loops in some section of the graph that it should have never got to (or some other crazy but realistic traversal path).