Hi,
no problem - yes, got it.
Its currently being worked on. We hope to have it available as part of the
next release - but you never know.
Currently the traverser can only stop on direct path FILTER expressions.
Not a native speaker as well, no problem ;-)
Cheers,
Willi
On Thursday, July
Hi,
Can you gist or pastebin a dump of your example graph so that I can have a
closer look at it myselves?
Cheers,
Willi
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an
Ok,
will be available with the next nightly devel documentation build or 3.0.3.
Thanks for taking the time to point this out - if you find more
explanations that irretate you, don't hesitate to follow up ;-)
Cheers,
Willi
On Thursday, July 14, 2016 at 1:02:39 AM UTC+2, The Bang Nguyen wrote:
If I looked to documentation
https://docs.arangodb.com/3.0/AQL/Graphs/Traversals.html
there should be something like this
Traversals on graphs:
Id Depth Vertex collections Edge collections Filter conditions
2 1..3circles edges `Path`.`edges`[0] ->
Hi Roman,
FILTERs are currently only pushed into the traversal engine when you filter
simple conditions on the path; Filtering on v & e are not intended to abort
traversals.
With ArangoDB 3.0 we introduced ANY and ALL in that context:
FILTER p.edges[*].type ALL == "cdp"
which will do what
Hi, I have graph (see attachment for example) with edges which have
property type. I want to traverse graph, but use only specific edges (for
example type == "cdp"). I tried following query:
for d in vDevice filter d.hostname == "lab54unl85AC172"
FOR v,e,p IN 1..1 any d GRAPH 'linkGraph'
