tinkerpop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From spmalle...@apache.org
Subject [21/32] tinkerpop git commit: Added a warning to docs around transaction
Date Wed, 28 Jun 2017 19:13:11 GMT
Added a warning to docs around transaction

Different graph providers have different kinds of support for transactions. Better to warn
users that might experience different approaches to transaction in various systems. CTR


Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/8bb99089
Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/8bb99089
Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/8bb99089

Branch: refs/heads/tp32-glv
Commit: 8bb99089af4000c6a719edd861f4913c659d7b71
Parents: 984b34d
Author: Stephen Mallette <spmva@genoprime.com>
Authored: Fri Jun 23 08:35:34 2017 -0400
Committer: Stephen Mallette <spmva@genoprime.com>
Committed: Fri Jun 23 08:35:34 2017 -0400

----------------------------------------------------------------------
 docs/src/reference/the-graph.asciidoc | 5 +++++
 1 file changed, 5 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/8bb99089/docs/src/reference/the-graph.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/reference/the-graph.asciidoc b/docs/src/reference/the-graph.asciidoc
index 063c174..d1e341e 100644
--- a/docs/src/reference/the-graph.asciidoc
+++ b/docs/src/reference/the-graph.asciidoc
@@ -198,6 +198,11 @@ a transactional leak does occur between requests somehow, a fresh transaction
is
 TIP: The `tx()` method is on the `Graph` interface, but it is also available on the `TraversalSource`
spawned from a
 `Graph`.  Calls to `TraversalSource.tx()` are proxied through to the underlying `Graph` as
a convenience.
 
+WARNING: TinkerPop provides for basic transaction control, however, like many aspects of
TinkerPop, it is up to the
+graph system provider to choose the specific aspects of how their implementation will work
and how it fits into the
+TinkerPop stack. Be sure to understand the transaction semantics of the specific graph implementation
that is being
+utilized as it may present differing functionality than described here.
+
 Configuring
 ~~~~~~~~~~~
 


Mime
View raw message