transaction.rb in google-cloud-spanner-v1-0.5.0

- old
+ new

@@ -84,11 +84,11 @@
         # {::Google::Cloud::Spanner::V1::Spanner::Client#commit Commit}. At any time before
         # {::Google::Cloud::Spanner::V1::Spanner::Client#commit Commit}, the client can send a
         # {::Google::Cloud::Spanner::V1::Spanner::Client#rollback Rollback} request to abort the
         # transaction.
         #
-        # ### Semantics
+        # ## Semantics
         #
         # Cloud Spanner can commit the transaction if all read locks it acquired
         # are still valid at commit time, and it is able to acquire write
         # locks for all writes. Cloud Spanner can abort the transaction for any
         # reason. If a commit attempt returns `ABORTED`, Cloud Spanner guarantees
@@ -97,11 +97,11 @@
         # Unless the transaction commits, Cloud Spanner makes no guarantees about
         # how long the transaction's locks were held for. It is an error to
         # use Cloud Spanner locks for any sort of mutual exclusion other than
         # between Cloud Spanner transactions themselves.
         #
-        # ### Retrying Aborted Transactions
+        # ## Retrying Aborted Transactions
         #
         # When a transaction aborts, the application can choose to retry the
         # whole transaction again. To maximize the chances of successfully
         # committing the retry, the client should execute the retry in the
         # same session as the original attempt. The original session's lock
@@ -113,11 +113,11 @@
         # short period before successfully committing. Thus, it is not a good
         # idea to cap the number of retries a transaction can attempt;
         # instead, it is better to limit the total amount of wall time spent
         # retrying.
         #
-        # ### Idle Transactions
+        # ## Idle Transactions
         #
         # A transaction is considered idle if it has no outstanding reads or
         # SQL queries and has not started a read or SQL query within the last 10
         # seconds. Idle transactions can be aborted by Cloud Spanner so that they
         # don't hold on to locks indefinitely. In that case, the commit will
@@ -163,11 +163,11 @@
         # or read-write transaction, because they are able to execute far
         # from the leader replica.
         #
         # Each type of timestamp bound is discussed in detail below.
         #
-        # ### Strong
+        # ## Strong
         #
         # Strong reads are guaranteed to see the effects of all transactions
         # that have committed before the start of the read. Furthermore, all
         # rows yielded by a single read are consistent with each other -- if
         # any part of the read observes a transaction, all parts of the read
@@ -179,11 +179,11 @@
         # reads should be executed within a transaction or at an exact read
         # timestamp.
         #
         # See {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#strong TransactionOptions.ReadOnly.strong}.
         #
-        # ### Exact Staleness
+        # ## Exact Staleness
         #
         # These timestamp bounds execute reads at a user-specified
         # timestamp. Reads at a timestamp are guaranteed to see a consistent
         # prefix of the global transaction history: they observe
         # modifications done by all transactions with a commit timestamp <=
@@ -201,11 +201,11 @@
         # boundedly stale reads usually return fresher results.
         #
         # See {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#read_timestamp TransactionOptions.ReadOnly.read_timestamp} and
         # {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#exact_staleness TransactionOptions.ReadOnly.exact_staleness}.
         #
-        # ### Bounded Staleness
+        # ## Bounded Staleness
         #
         # Bounded staleness modes allow Cloud Spanner to pick the read timestamp,
         # subject to a user-provided staleness bound. Cloud Spanner chooses the
         # newest timestamp within the staleness bound that allows execution
         # of the reads at the closest available replica without blocking.
@@ -231,10 +231,10 @@
         # read-only transactions.
         #
         # See {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#max_staleness TransactionOptions.ReadOnly.max_staleness} and
         # {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#min_read_timestamp TransactionOptions.ReadOnly.min_read_timestamp}.
         #
-        # ### Old Read Timestamps and Garbage Collection
+        # ## Old Read Timestamps and Garbage Collection
         #
         # Cloud Spanner continuously garbage collects deleted and overwritten data
         # in the background to reclaim storage space. This process is known
         # as "version GC". By default, version GC reclaims versions after they
         # are one hour old. Because of this, Cloud Spanner cannot perform reads