Skip to content

docs(api2): interleaved SQLite commits may violate single-round-trip consistency #7734

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

Open
cfm wants to merge 1 commit into
base: develop
Choose a base branch
from
+12 −2
Open

docs(api2): interleaved SQLite commits may violate single-round-trip consistency #7734

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 12 additions & 2 deletions API2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,8 +233,18 @@ E_n\}$; and

4. $C$'s index SHOULD match $S$'s index without a subsequent synchronization.

This property does not hold for resubmitted events (returning HTTP `208 Already
Reported)`. A subsequent synchronization MAY be necessary for the client to
This property does not hold:

- when the server has multiple active clients. Because this API reuses some
utility functions from the v1 Journalist API, it inherits the inconsistent
transaction isolation of the latter's use of a shared SQLAlchemy session, which
may cause side effects of events received very close in time to be interleaved
at the SQLite level.

- for resubmitted events, which return an HTTP `208 Already Reported` status
without the full result of the event.

In these cases, a subsequent synchronization MAY be necessary for the client to
"catch up" to the effects of accepted events.

#### Snowflake IDs
Expand Down