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

Cypher: Make updates check whether their target node(s) exist #343

Closed
wants to merge 6 commits into from

Conversation

szarnyasg
Copy link
Member

@szarnyasg szarnyasg changed the title Cypher: Make updates check whether the target node(s) exist Cypher: Make updates check whether their target node(s) exist Nov 7, 2022
@szarnyasg
Copy link
Member Author

szarnyasg commented Apr 21, 2023

The failure is caused by an entry which is inserted and deleted in the same batch:

$ ag 2336465348864
out-sf1/graphs/csv/bi/composite-merged-fk/inserts/dynamic/Comment/batch_id=2012-11-29/part-00000-ae9b25c5-14a3-4ba4-a54c-946e9fcd296d.c000.csv
19:2012-11-29T02:55:16.321+00:00|2336465348864|31.6.75.90|Internet Explorer|ok|2|2199023265458|75|2336465348858|

out-sf1/graphs/csv/bi/composite-merged-fk/deletes/dynamic/Comment/batch_id=2012-11-29/part-00000-068751da-9500-414b-93c9-81d776a2f2e9.c000.csv
2:2012-11-29T02:55:26.331+00:00|2336465348864

It's worth noting that the entity is deleted 10.010 seconds after being inserted.

The reason of the failure may be due to the isolation level (read committed) used by the Cypher implementation being insufficient for concurrent writes. This needs more investigation.

@szarnyasg szarnyasg closed this Sep 1, 2023
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

Successfully merging this pull request may close these issues.

Cypher: Updates with non-existent target nodes should fail
2 participants