8000 Add edgeCollections and vertexCollections traversal options. by dhly-etc · Pull Request #345 · arangodb/docs · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Dec 13, 2023. It is now read-only.

Conversation

@dhly-etc
Copy link
Contributor

Document the recently added vertexCollections and edgeCollections restrictions for traversal options.

@dhly-etc dhly-etc requested a review from jsteemann February 25, 2020 17:28
@dhly-etc dhly-etc self-assigned this Feb 25, 2020
@jsteemann jsteemann requested a review from Simran-B February 25, 2020 17:46
@Simran-B
Copy link
Collaborator

@danielhlarkin

I created anonymous graph A/1 --[x/?]--> B/2 --[y/?]--> C/3 to see what happens if you restrict the edge collections using the new option in addition to specifying the edge collection set.

FOR v,e,p IN 0..10 OUTBOUND "A/1" x, y
OPTIONS { edgeCollections: ["x"], vertexCollections: ["A","B","C"] }
RETURN v._key

Looks like the option can be used to further restrict the traversal, which is fine. Just something we might want to document.

Something I noticed in the query explain:

Traversals on graphs:
 Id  Depth  Vertex collections  Edge collections  Options                                                            Filter / Prune Conditions
 2   0..10                      x                 uniqueVertices: none, uniqueEdges: path, vertexCollections: A,B,C

There are columns for vertex collections and edge collections, but only the edge collection "x" is listed the latter. The vertex collections are listed in the options column instead. Shouldn't it be like this?

Traversals on graphs:
 Id  Depth  Vertex collections  Edge collections  Options                                  Filter / Prune Conditions
 2   0..10  A,B,C               x                 uniqueVertices: none, uniqueEdges: path

@Simran-B Simran-B merged commit ef2e6a5 into master Mar 26, 2020
@Simran-B Simran-B deleted the feature/traversal-collection-restrictions branch March 26, 2020 12:55
@Simran-B Simran-B added this to the 3.7 milestone Mar 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

0