[Bigdata-commit] SF.net SVN: bigdata:[3803] branches/QUADS_QUERY_BRANCH/bigdata/src/java/com /bigdata

[<tho...@us...>]

Revision: 3803
          http://bigdata.svn.sourceforge.net/bigdata/?rev=3803&view=rev
Author:   thompsonbry
Date:     2010-10-17 11:09:45 +0000 (Sun, 17 Oct 2010)

Log Message:
-----------
javadoc edits (spelling errors).

Modified Paths:
--------------
    branches/QUADS_QUERY_BRANCH/bigdata/src/java/com/bigdata/journal/ITransactionService.java
    branches/QUADS_QUERY_BRANCH/bigdata/src/java/com/bigdata/service/AbstractTransactionService.java

Modified: branches/QUADS_QUERY_BRANCH/bigdata/src/java/com/bigdata/journal/ITransactionService.java
===================================================================
--- branches/QUADS_QUERY_BRANCH/bigdata/src/java/com/bigdata/journal/ITransactionService.java	2010-10-15 12:17:18 UTC (rev 3802)
+++ branches/QUADS_QUERY_BRANCH/bigdata/src/java/com/bigdata/journal/ITransactionService.java	2010-10-17 11:09:45 UTC (rev 3803)
@@ -65,7 +65,7 @@
  * global release time - the earliest commit time from which a transaction may
  * read. Under dire circumstances (disk shortage) the transaction manager MAY
  * choose to abort transactions and advance the release time in order to permit
- * the release of locked resources and the reclaimation of their space on local
+ * the release of locked resources and the reclamation of their space on local
  * disk.
  * </p>
  * <h2>Centralized transaction manager service</h2>
@@ -87,8 +87,8 @@
  * time, rendering views of earlier states of the database unavailable.
  * </p>
  * <p>
- * The transaction identifier is the transaction <em>start time</em>. The
- * transaction start time is choosen from among those distinct timestamps
+ * The transaction identifier codes the transaction <em>start time</em>. The
+ * transaction start time is chosen from among those distinct timestamps
  * available between the specified commit time and the next commit time on the
  * database. Successive read-write transactions must be assigned transaction
  * identifiers whose absolute value is strictly increasing - this requirement is
@@ -100,10 +100,10 @@
  * identifiers may be directly used as commit times when reading on a local
  * store. Read-write transaction identifiers must have their sign bit cleared in
  * order to read from their ground state (the commit point corresponding to
- * their transaction start time) and unmodified transaction identifier is used
- * to access their mutable view (the view comprised of the write set of the
+ * their transaction start time) but the unmodified transaction identifier is 
+ * used to access their mutable view (the view comprised of the write set of the
  * transaction super imposed on the ground state such that writes, overwrites,
- * and deletes are visible to the view).
+ * and deletes are visible in the view).
  * </p>
  * <p>
  * The symbolic value {@link ITx#READ_COMMITTED} and any <code>startTime</code>
@@ -257,7 +257,7 @@
      * operation isolated by a read-write transaction to execute with access to
      * the named resources (this applies only to distributed databases). The
      * declared resources are used in the commit phase of the read-write tx to
-     * impose a partial order on commits. That partial order guarentees that
+     * impose a partial order on commits. That partial order guarantees that
      * commits do not deadlock in contention for the same resources.
      * 
      * @param tx

Modified: branches/QUADS_QUERY_BRANCH/bigdata/src/java/com/bigdata/service/AbstractTransactionService.java
===================================================================
--- branches/QUADS_QUERY_BRANCH/bigdata/src/java/com/bigdata/service/AbstractTransactionService.java	2010-10-15 12:17:18 UTC (rev 3802)
+++ branches/QUADS_QUERY_BRANCH/bigdata/src/java/com/bigdata/service/AbstractTransactionService.java	2010-10-17 11:09:45 UTC (rev 3803)
@@ -633,7 +633,7 @@
      * 
      * @throws RuntimeException
      *             Wrapping {@link TimeoutException} if a timeout occurs
-     *             awaiting a start time which would satisify the request for a
+     *             awaiting a start time which would satisfy the request for a
      *             read-only transaction (this can occur only for read-only
      *             transactions which must contend for start times which will
      *             read from the appropriate historical commit point).
@@ -658,7 +658,7 @@
              * Higher concurrency will require relaxing constraints on atomic
              * state transitions governed by [lock]. Perhaps by introducing
              * additional locks that are more specific. I don't want to relax
-             * those constaints until I have a better sense of what must be
+             * those constraints until I have a better sense of what must be
              * exclusive operations.
              */
 
@@ -1115,7 +1115,7 @@
 	 * (commitTime-1) then compute and set the new releaseTime.
 	 * <p>
 	 * Note: This method was historically part of {@link #notifyCommit(long)}.
-	 * It was moved into its own method so it can be overriden for some unit
+	 * It was moved into its own method so it can be overridden for some unit
 	 * tests.
 	 * 
 	 * @throws IllegalMonitorStateException
@@ -1203,10 +1203,10 @@
      * 
      * @throws InterruptedException
      *             if interrupted while awaiting a start time which would
-     *             satisify the request.
+     *             satisfy the request.
      * @throws InterruptedException
      *             if a timeout occurs while awaiting a start time which would
-     *             satisify the request.
+     *             satisfy the request.
      */
     protected long assignTransactionIdentifier(final long timestamp)
             throws InterruptedException, TimeoutException {
@@ -1217,7 +1217,7 @@
              * When timestamp is ZERO (0L), this simply returns the next
              * distinct timestamp (with its sign bit flipped).
              * 
-             * Note: This is guarenteed to be a valid start time since it is LT
+             * Note: This is guaranteed to be a valid start time since it is LT
              * the next possible commit point for the database.
              * 
              * Note: When we validate, we will read from [-startTime] and the
@@ -1338,7 +1338,7 @@
 
             /*
              * Note: If there is no successor of the desired commit point then
-             * we can just return the next timestamp. It is guarenteed to be GT
+             * we can just return the next timestamp. It is guaranteed to be GT
              * the desired commit time and LT the next commit point. [Note: this
              * case is in fact handled above so you should not get here.]
              */


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.