Interface Graph

    • Method Detail

      • addVertex

        Vertex addVertex​(Object... keyValues)
        Add a Vertex to the graph given an optional series of key/value pairs. These key/values must be provided in an even number where the odd numbered arguments are String property keys and the even numbered arguments are the related property values.
        keyValues - The key/value pairs to turn into vertex properties
        The newly created vertex
      • addVertex

        default Vertex addVertex​(String label)
        Add a Vertex to the graph with provided vertex label.
        label - the label of the vertex
        The newly created labeled vertex
      • compute

        <C extends GraphComputer> C compute​(Class<C> graphComputerClass)
                                     throws IllegalArgumentException
        Declare the GraphComputer to use for OLAP operations on the graph. If the graph does not support graph computer then an UnsupportedOperationException is thrown.
        graphComputerClass - The graph computer class to use.
        A graph computer for processing this graph
        IllegalArgumentException - if the provided GraphComputer class is not supported.
      • traversal

        default <C extends TraversalSource> C traversal​(Class<C> traversalSourceClass)
        Generate a TraversalSource using the specified TraversalSource class. The reusable TraversalSource provides methods for spawning Traversal instances.
        Type Parameters:
        C - The traversal source class
        traversalSourceClass - The traversal source class
      • edges

        Iterator<Edge> edges​(Object... edgeIds)
        Get the Edge objects in this graph with the provided edge ids or Edge objects. If no ids are provided, get all edges. Note that an edge identifier does not need to correspond to the actual id used in the graph. It needs to be a bit more flexible than that in that given the Graph.Features around id support, multiple arguments might be applicable here.

        If the graph return true for Graph.Features.ElementFeatures.supportsNumericIds() then it should support filters as with:

        • g.edges(e)
        • g.edges(
        • g.edges(1)
        • g.edges(1L)
        • g.edges(1.0d)
        • g.edges(1.0f)
        • g.edges("1")

        If the graph return true for Graph.Features.ElementFeatures.supportsCustomIds() ()} then it should support filters as with:

        • g.edges(e)
        • g.edges(
        • g.edges(

        If the graph return true for Graph.Features.ElementFeatures.supportsAnyIds() ()} then it should support filters as with:

        • g.edges(e)
        • g.edges(

        If the graph return true for Graph.Features.ElementFeatures.supportsStringIds() ()} then it should support filters as with:

        • g.edges(e)
        • g.edges(
        • g.edges("id")
        edgeIds - the ids of the edges to get
        an Iterator of edges that match the provided edge ids
      • tx

        Transaction tx()
        Configure and control the transactions for those graphs that support this feature.
      • tx

        default <Tx extends Transaction> Tx tx​(Class<Tx> txClass)
        Configure and control the transactions for those graphs that support this feature. Graphs that support multiple transaction models can use this method expose different sorts of Transaction implementations.
      • close

        void close()
            throws Exception
        Closing a Graph is equivalent to "shutdown" and implies that no further operations can be executed on the instance. Users should consult the documentation of the underlying graph database implementation for what this "shutdown" will mean in general and, if supported, how open transactions are handled. It will typically be the end user's responsibility to synchronize the thread that calls close() with other threads that are accessing open transactions. In other words, be sure that all work performed on the Graph instance is complete prior to calling this method.

        TinkerPop does not enforce any particular semantics with respect to "shutdown". It is up to the graph provider to decide what this method will do.

        Specified by:
        close in interface AutoCloseable
      • io

        default <I extends Io> I io​(Io.Builder<I> builder)
        As of release 3.4.0, partially replaced by Notice doesn't support read operation from or write operation to Thus for readers or writers which need this functionality are safe to use this deprecated method. There is no intention to remove this method unless all the functionality is replaced by the `io` step of GraphTraversalSource.
        Construct a particular Io implementation for reading and writing the Graph and other data. End-users will "select" the Io implementation that they want to use by supplying the Io.Builder that constructs it. In this way, Graph vendors can supply their IoRegistry to that builder thus allowing for custom serializers to be auto-configured into the Io instance. Registering custom serializers is particularly useful for those graphs that have complex types for Element identifiers.

        For those graphs that do not need to register any custom serializers, the default implementation should suffice. If the default is overridden, take care to register the current graph via the Io.Builder.graph(Graph) method.
      • variables

        Graph.Variables variables()
        A collection of global Graph.Variables associated with the graph. Variables are used for storing metadata about the graph.
        The variables associated with this graph
      • configuration

        org.apache.commons.configuration2.Configuration configuration()
        Get the Configuration associated with the construction of this graph. Whatever configuration was passed to is what should be returned by this method.
        the configuration used during graph construction.