asterixdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ima...@apache.org
Subject [1/7] incubator-asterixdb git commit: updated the documentation for the transaction model on behalf of youngseok
Date Fri, 24 Apr 2015 19:08:54 GMT
Repository: incubator-asterixdb
Updated Branches:
  refs/heads/documentation [created] 6d8f4d54f


updated the documentation for the transaction model on behalf of youngseok


Project: http://git-wip-us.apache.org/repos/asf/incubator-asterixdb/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-asterixdb/commit/67674e67
Tree: http://git-wip-us.apache.org/repos/asf/incubator-asterixdb/tree/67674e67
Diff: http://git-wip-us.apache.org/repos/asf/incubator-asterixdb/diff/67674e67

Branch: refs/heads/documentation
Commit: 67674e67060513c1a62429b43d38a91c4dac7b39
Parents: b9c7a72
Author: zheilbron <zheilbron@gmail.com>
Authored: Wed Jan 29 14:15:28 2014 -0800
Committer: zheilbron <zheilbron@gmail.com>
Committed: Wed Jan 29 15:48:35 2014 -0800

----------------------------------------------------------------------
 asterix-doc/src/site/markdown/aql/manual.md | 7 ++++---
 asterix-doc/src/site/markdown/aql/primer.md | 4 ++++
 2 files changed, 8 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-asterixdb/blob/67674e67/asterix-doc/src/site/markdown/aql/manual.md
----------------------------------------------------------------------
diff --git a/asterix-doc/src/site/markdown/aql/manual.md b/asterix-doc/src/site/markdown/aql/manual.md
index 882d331..ab99f16 100644
--- a/asterix-doc/src/site/markdown/aql/manual.md
+++ b/asterix-doc/src/site/markdown/aql/manual.md
@@ -446,12 +446,13 @@ It is useful to note that if the set were instead the empty set, the
first expre
                       | SetStatement
                       | InsertStatement
                       | DeleteStatement
-                      | Query
+                      | Query                      
 
 In addition to expresssions for queries, AQL supports a variety of statements for data
 definition and manipulation purposes as well as controlling the context to be used in
-evaluating AQL expressions. 
-This section details the statement side of the AQL language.
+evaluating AQL expressions. AQL supports record-level ACID transactions that begin and terminate
implicitly for each record inserted, deleted, or searched while a given AQL statement is being
executed.
+
+This section details the statements supported in the AQL language.
 
 ### Declarations
  

http://git-wip-us.apache.org/repos/asf/incubator-asterixdb/blob/67674e67/asterix-doc/src/site/markdown/aql/primer.md
----------------------------------------------------------------------
diff --git a/asterix-doc/src/site/markdown/aql/primer.md b/asterix-doc/src/site/markdown/aql/primer.md
index 92fcb01..b254e46 100644
--- a/asterix-doc/src/site/markdown/aql/primer.md
+++ b/asterix-doc/src/site/markdown/aql/primer.md
@@ -883,6 +883,10 @@ To achieve the effect of an update, two statements are currently needed---one
to
 dataset where it resides, and another to insert the new replacement record (with the same
primary key but with
 different field values for some of the associated data content).
 
+### Transaction Support
+
+AsterixDB supports record-level ACID transactions that begin and terminate implicitly for
each record inserted, deleted, or searched while a given AQL statement is being executed.
This is quite similar to the level of transaction support found in today's NoSQL stores. AsterixDB
does not support multi-statement transactions, and in fact an AQL statement that involves
multiple records can itself involve multiple independent record-level transactions. An example
consequence of this is that, when an AQL statement attempts to insert 1000 records, it is
possible that the first 800 records could end up being committed while the remaining 200 records
fail to be inserted. This situation could happen, for example, if a duplicate key exception
occurs as the 801st insertion is attempted. If this happens, AsterixDB will report the error
(e.g., a duplicate key exception) as the result of the offending AQL insert statement, and
the application logic above will need to take the appropriate action(s
 ) needed to assess the resulting state and to clean up and/or continue as appropriate.
+
 ## Further Help ##
 That's it  You are now armed and dangerous with respect to semistructured data management
using AsterixDB.
 


Mime
View raw message