[
https://issues.apache.org/jira/browse/TINKERPOP3-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009465#comment-15009465
]
ASF GitHub Bot commented on TINKERPOP3-679:
-------------------------------------------
Github user twilmes commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/145#issuecomment-157501940
Tests all pass and I tried a variety of traversals out in the shell and
explain worked as expected. Padding between columns stays correct so
formatting is good. It can get hard to read when the traversal is long but
since it returns a TraversalExplanation, a user could prettify it however they
wanted quite easily (json, csv, etc.)
+1
> Debuggable Traversal
> --------------------
>
> Key: TINKERPOP3-679
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-679
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
>
> I'd like to be able to put a {{Traversal}} into "debug mode".
> {{TraversalStrategy}} application is a bit too mysterious, making it hard to
> figure out why a {{Traversal}} is failing. In a recent debug session, the
> problem was only sorted out after we looked at the order in which strategies
> were applied and even then it was a bit tricky to really understand what was
> happening.
> If the {{Traversal}} were in this "debug mode" it could give us insight into
> that strategy application process which would mean at least the following:
> * Display the order in which strategies were applied
> * For each strategy applied, display the {{toString()}} of the {{Traversal}}
> at that stage.
> A developer could then logically see what's in the magic and recognize that
> strategy 7 is ovewriting what strategy 2 is doing or that strategy 4 is
> executing before strategy 3 somehow.
> Not sure what the best way is to implement this. A straightforward solution
> with an environment variable check and println in {{applyStrategies}} seemed
> too "cheap" though kinda nice because very little would change and that
> output would come as part of the standard {{Traversal}} execution. Other
> (better) ways?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
