Search by property

Jump to navigation Jump to search

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "Step text" with value "Splits the traverser". Since there have been only a few results, also nearby values are displayed.

Showing below up to 16 results starting with #1.

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)


    

List of results

    • Gremlin  + (The coalesce()-step evaluates the provided traversals in order and returns the first traversal that emits at least one element.)
    • Gremlin  + (The outV step maps the current edges to the outgoing Vertices.)
    • Gremlin  + (There are situations when the traversal stThere are situations when the traversal stream needs a "barrier" to aggregate all the objects and emit a computation that is a function of the aggregate. The fold()-step (map) is one particular instance of this. Please see unfold()-step for the inverse functionality.fold()-step for the inverse functionality.)
    • Gremlin  + (can only be used with remote traversals to Gremlin Server or RGPs. It starts a promise to execute a function on the current Traversal that will be completed in the future.)
    • Gremlin  + (counts the total number of represented traversers in the streams (i.e. the bulk count).)
    • Gremlin  + (determines whether there are available results)
    • Gremlin  + (ensures that all provided traversals yield a result)
    • Gremlin  + (ensures that at least one of the provided traversals yield a result.)
    • Gremlin  + (fill(collection) will put all results in the provided collection and return the collection when complete.)
    • Gremlin  + (filters elements that fullfill the given predicate. Variant: Filters elements that are equal to the given Object.)
    • Gremlin  + (filters the current object based on eitherfilters the current object based on either the object itself (Scope.local) or the path history of the object (Scope.global) (filter). This step is typically used in conjunction with either [[#match Step]] or [[#select Step|select()-step]], but can be used in isolation.[[#select Step|select()-step]], but can be used in isolation.)
    • Gremlin  + (filters vertices, edges, and vertex properties based on their properties. This step has quite a few variations.)
    • Gremlin  + (is not a real step, but a "step modulator" similar to by() and option(). With as(), it is possible to provide a label to the step that can later be accessed by steps and data structures that make use of such labels — e.g., select(), match(), and path)
    • Gremlin  + (is not an actual step, but instead is a "sis not an actual step, but instead is a "step-modulator" similar to as() and option(). If a step is able to accept traversals, functions, comparators, etc. then by() is the means by which they are added. The general pattern is step().by()…by(). Some steps can only accept one by() while others can take an arbitrary amount.while others can take an arbitrary amount.)
    • Gremlin  + (is not an actual step, but is instead a step modulator for [[#repeat Step|repeat()]] (find more documentation on the emit() there).)