Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ACID Tests. AtomicityC and AtomicityRB checks are confusing #246

Open
ArnauPrat opened this issue Apr 3, 2024 · 0 comments
Open

ACID Tests. AtomicityC and AtomicityRB checks are confusing #246

ArnauPrat opened this issue Apr 3, 2024 · 0 comments

Comments

@ArnauPrat
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant