updated the complex filtering in traversal-induced-values.asciidoc with a more 
simple where().by() clause per @spmallette's request.

Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/82a1bc00
Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/82a1bc00
Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/82a1bc00

Branch: refs/heads/TINKERPOP-1404
Commit: 82a1bc0083a49716f15f168a1929f3ee3eb4a209
Parents: 9ef30f0
Author: Marko A. Rodriguez <okramma...@gmail.com>
Authored: Thu Sep 15 05:35:13 2016 -0600
Committer: Marko A. Rodriguez <okramma...@gmail.com>
Committed: Thu Sep 15 09:58:53 2016 -0600

 .../recipes/traversal-induced-values.asciidoc   | 32 +++++---------------
 1 file changed, 8 insertions(+), 24 deletions(-)

diff --git a/docs/src/recipes/traversal-induced-values.asciidoc 
index 6adefc7..74402b6 100644
--- a/docs/src/recipes/traversal-induced-values.asciidoc
+++ b/docs/src/recipes/traversal-induced-values.asciidoc
@@ -40,37 +40,21 @@ g.V(marko).out('knows').has('age', 
 The downside to this approach is that it takes two separate traversals to 
answer the question. Ideally, there should
 be a single traversal, that can query "marko" once, determine his `age` and 
then use that for the value supplied to
-filter the people he knows. In this way the _value_ for the `age` filter is 
_induced_ from the `Traversal` itself.
+filter the people he knows. In this way the _value_ for the `age` in the 
`has()`-filter is _induced_ from the `Traversal`
-g.V().has('name','marko').as('marko').         <1>
-  out('knows').as('friend').                   <2>
-  filter(select('marko','friend').by('age').   <3>
-         where('friend', gt('marko'))).        <4>
+g.V().has('name','marko').as('marko').      <1>
+  out('knows').as('friend').                <2>
+    where('friend', gt('marko')).by('age'). <3>
 <1> Find the "marko" `Vertex` and label it as "marko".
-<2> Traverse out on the "knows" edges to the adjacent `Vertex` and label it as 
-<3> Filter the incoming "person" vertices. It is within this filter, that the 
traversal induced values are utilized.
-The inner `select` grabs the "marko" vertex and the current "friend". The `by` 
modulator extracts the "age" from both
-of those vertices which yields a `Map` with two keys, "marko" and "friend", 
where the value of each is the "age".
-<4> The `Map` produced in the previous step can then be filtered with `where` 
to only return a result if the "friend"
-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 
-    __.as('marko').values('age').as('a'),
-    __.as('marko').out('knows').as('friend'),
-    __.as('friend').values('age').as('b')
-  ).where('b', gt('a')).select('friend').
-  values('name')
+<2> Traverse out on the "knows" edges to the adjacent `Vertex` and label it as 
+<3> Continue to traverser only if Marko's current friend is older than him.
+<4> Get the name of Marko's older friend.
 Traversal induced values are not just for filtering. They can also be used 
when writing the values of the properties
 of one `Vertex` to another:

Reply via email to