Hello,
We just added an explain()-step to Gremlin. It is a terminal, side-effect step
like drop(). However, until drop(), it returns a TraversalExplanation object
that has a pretty toString().
http://tinkerpop.incubator.apache.org/docs/3.1.1-SNAPSHOT/#explain-step
In short, you can see the sort order of the traversal strategies (compilers)
and you can see how each strategy alters the structure of the traversal. What
is interesting is that I found a bug in our strategy ordering when I was
writing up the documentation as explain() made it obvious when and how each
strategy was applied.
SIDE-NOTE: For 3.2.0 we will be pulling out MatchAlgorithm to a general type of
strategy called RuntimeTraversalStrategy and when that happens, we will get
clever with how that will be reflected in explain().
Enjoy,
Marko.
http://markorodriguez.com
