Hi Jesse,
your explanation was very helpful as I am trying to crawl through very old
documentation.
How these values (undefined,exclude,prune and [prune,exclude]) can be
translated in a FILTER statement since in ArangoDB 3 the traversal graphs
cannot be used in AQLs?
How can prune and exclude can be used in a query like "FOR v, e, p IN 1..10
INBOUND|OUTBOUND|ANY id graph" with FILTER without losing any flexibility a
UDF can provide?
On Friday, January 17, 2014 at 11:55:16 AM UTC+2, Michael Hackstein wrote:
>
> Hi Jesse,
>
> there is an endpoint for specific vertex filtering available in the
> traversal API.
> Called "filter".
> You are using "expandFilter" which is dedicated to edges.
> So according from your example text you could use:
>
> function vertexFilter (config, vertex, path) {
> if (vertex.isDeleted === true) {
> return ["prune", "exclude"];
> }
> return null;
> }
> and
> [...]
> config.filter = vertexFilter;
> [...]
>
>
> More Information from our Documentation:
>
>
>
> - filter: vertex filter function. The function signature is function
> (config, vertex, path). It may return one of the following values:
> - undefined: vertex will be included in the result and connected
> edges will be traversed
> - exclude: vertex will not be included in the result and connected
> edges will be traversed
> - prune: vertex will be included in the result but connected edges
> will not be traversed
> - [ prune, exclude ]: vertex will not be included in the result and
> connected edges will not be returned
>
>
>
> Best
> Michael
>
--
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 email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
