This is an automated email from the ASF dual-hosted git repository.

spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git


The following commit(s) were added to refs/heads/master by this push:
     new a45da922db Scope Considering Transactions section to Gremlin Server
a45da922db is described below

commit a45da922db327cf7dce1f18f8008b15523d9c4ce
Author: Stephen Mallette <[email protected]>
AuthorDate: Thu Jul 23 18:15:25 2026 +0000

    Scope Considering Transactions section to Gremlin Server
    
    The Considering Transactions section lives within the Gremlin Server
    documentation, where each request is wrapped in its own transaction and
    auto-committed on success. Its intro sentence framed transactions
    generally, which made the per-request auto-commit statements (e.g. a bare
    g.addV being persisted without an explicit commit()) read as applying to
    all execution contexts. That is not accurate for embedded/console use of
    a transactional graph such as TinkerTransactionGraph, where the
    transaction stays open and a rollback() discards the change. Reword the
    intro sentence to scope the section to traversals sent to Gremlin Server,
    which makes the existing statements correct without other changes.
    
    Assisted-by: Kiro:claude-opus-4.8
---
 docs/src/reference/gremlin-applications.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/reference/gremlin-applications.asciidoc 
b/docs/src/reference/gremlin-applications.asciidoc
index fb766ba0cf..e2ebb0e3dd 100644
--- a/docs/src/reference/gremlin-applications.asciidoc
+++ b/docs/src/reference/gremlin-applications.asciidoc
@@ -2042,7 +2042,7 @@ above with the use of the `maximumSize`.
 [[considering-transactions]]
 ==== Considering Transactions
 
-Every traversal executes within a transaction. TinkerPop distinguishes between 
two modes:
+Every traversal sent to Gremlin Server executes within a transaction. There 
are two transactional modes to distinguish from each other:
 
 * *Implicit transactions* are the default. Each traversal submitted through 
`g` is a self-contained unit of work. All
 graphs participate in implicit transactions. When the graph supports explicit 
transactions, implicit transactions are

Reply via email to