Added new recipe for Traversal Induced Values. #371
Conversation
|
Please ignore the failing test: IdentityRemovalStrategyTest$PerformanceTest>TraversalStrategyPerformanceTest.shouldBeFaster:107 null that's an issue raised elsewhere: https://issues.apache.org/jira/browse/TINKERPOP-1390 |
|
I might be missing something silly here, but It looks like you need to commit |
|
Sorry - forgot to add the file @twilmes - fixed up the commit and force pushed. |
|
Looks good, nice choice for a recipe. VOTE: +1 |
|
VOTE +1. This got me to thinking that we really need to start to extend other steps (beyond the |
| age is greater than the "marko" age. If this is successful, then the `filter` step from the previous line will succeed | ||
| and allow the "friend" vertex to pass through. | ||
|
|
||
| This traversal could also be written declaratively with `match` step as follows: |
There was a problem hiding this comment.
Should there be any discussion of the possible performance differences between the 2 approaches? Or is that mostly a system-specific discussion?
There was a problem hiding this comment.
I thought about going into more detail there, but opted not to. I kinda thought that if we wanted that sort of content that it didn't belong in a recipe but in reference docs. It seemed a little out of scope of the recipe.
5 participants
Just a documentation addition. I learned that it's not so good to CTR these as there is sometimes good feedback on Gremlin code that should be incorporated and a PR is the best way to go about gathering that feedback.
VOTE +1