spmallette opened a new pull request, #3571:
URL: https://github.com/apache/tinkerpop/pull/3571
The `subgraph()`-step section cautions that a TinkerGraph subgraph's
elements (`TinkerVertex`/`TinkerEdge`) can not be used directly in Gremlin
running against the original graph, and presents this example as one that
"would likely return an error":
```
Vertex v = sg.V().has('name','marko').next();
List<Vertex> vertices = g.V(v).out().toList();
```
For the example as shown, though, the original graph is also a TinkerGraph.
In that case TinkerGraph looks vertices up by their identifier, so the
reference resolves and `g.V(v).out()` returns the expected result rather than
erroring. The warning is accurate only when the original graph is a different
implementation that may not recognize a foreign `TinkerVertex`.
This reduces the caveat paragraph and its callout to
implementation-dependent framing:
- When the original graph is also a TinkerGraph (as in the modern graph
example shown), the reference resolves by identifier and the traversal succeeds.
- When the original graph is a different implementation, it may reject a
foreign `TinkerVertex` and could return an error.
Scope is limited to the caveat paragraph and its second callout. The
edge-induced subgraph examples above and the `ReferenceVertex`/`id()`
portable-recommendation block below are unchanged, and the illustrative snippet
remains non-executed text. The reference book was rendered locally to confirm
it builds and reads coherently.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
