Skip to content

Correct note about supported runtime for transaction subqueries #1300

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Jun 11, 2025
Merged

Correct note about supported runtime for transaction subqueries #1300

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b37941e
Correct note about supported runtime for transaction subqueries
henriknyman Jun 10, 2025
9b1072f
new location
JPryce-Aklundh Jun 11, 2025
501a81a
Merge branch 'dev' into cit-retry-note
JPryce-Aklundh Jun 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -554,9 +554,6 @@ If the transaction still fails after the maximum duration, the failure is handle
It is particularly suitable for xref:subqueries/subqueries-in-transactions.adoc#concurrent-transactions[concurrent transactions], reducing the likelihood of a query failing due to xref:subqueries/subqueries-in-transactions.adoc#deadlocks[deadlocks].


[NOTE]
Queries using `ON ERROR RETRY` can currently only use the xref:planning-and-tuning/runtimes/concepts.adoc#runtimes-slotted-runtime[slotted runtime].

.Basic retry with default duration
=====

Expand Down Expand Up @@ -788,11 +785,13 @@ By default, `CALL { ... } IN TRANSACTIONS` is single-threaded; one CPU core is u
However, `CALL` subqueries can also execute batches in parallel by appending `IN [n] CONCURRENT TRANSACTIONS`, where `n` is a concurrency value used to set the maximum number of transactions that can be executed in parallel.
This allows `CALL` subqueries to utilize multiple CPU cores simultaneously, which can significantly reduce the time required to execute a large, outer transaction.

[NOTE]
The concurrency value is optional.
If not specified, a default value based on the amount of available CPU cores will be chosen.
If a negative number is specified (which can only be done through a parameter), the concurrency will be the number of available CPU cores reduced by the absolute value of that number.

[NOTE]
Queries using `CONCURRENT TRANSACTIONS` can currently only use the xref:planning-and-tuning/runtimes/concepts.adoc#runtimes-slotted-runtime[slotted runtime].

.Load a CSV file in concurrent transactions
====

Expand Down