You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AtomicityC and AtomicityRB acid tests are a bit confusing.
The spec says:
"Tests are executed as follows: (i) load a graph of Person nodes (Listing 8.1) each
with a unique id and a set of emails; (ii) a client executes a full graph scan counting the number of nodes,
edges and emails (Listing 8.4) using the result to initialize a counter committed; (iii) N transaction instances
(Listing 8.2, Listing 8.3) of the required test are then executed, committed is incremented for each successful
commit; (iii) repeat the full graph scan, storing the result in the variable finalState; (iv) perform the anomaly
check: committed=finalState"
The problem comes from Listing 8.4, where a Cypher query for the "check" is shown. That query does not count the number of edges as the text says.
The text was updated successfully, but these errors were encountered:
AtomicityC and AtomicityRB acid tests are a bit confusing.
The spec says:
"Tests are executed as follows: (i) load a graph of Person nodes (Listing 8.1) each
with a unique id and a set of emails; (ii) a client executes a full graph scan counting the number of nodes,
edges and emails (Listing 8.4) using the result to initialize a counter committed; (iii) N transaction instances
(Listing 8.2, Listing 8.3) of the required test are then executed, committed is incremented for each successful
commit; (iii) repeat the full graph scan, storing the result in the variable finalState; (iv) perform the anomaly
check: committed=finalState"
The problem comes from Listing 8.4, where a Cypher query for the "check" is shown. That query does not count the number of edges as the text says.
The text was updated successfully, but these errors were encountered: