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

Remove transaction metadata from bulk imports #118

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

josephschorr
Copy link
Member

The entire bulk import is a single transaction, and there is no message in which we can provide the metadata, so disallow it

The entire bulk import is a single transaction, and there is no message in which we can provide the metadata, so disallow it
Copy link
Contributor

@tstirrat15 tstirrat15 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The conversation was that ImportBulk and BulkImport both use streaming for network reasons, but the endpoint uses a single DB transaction per request to ensure that when you receive an error, you know what was and wasn't applied, which wouldn't be so easy if it were client streaming. We may revisit this, but in the meantime we'll use a header to get similar behavior out of the current implementation of the bulk endpoints.

@josephschorr josephschorr merged commit 8a6892e into authzed:main Oct 1, 2024
1 of 2 checks passed
@josephschorr josephschorr deleted the bulk-change branch October 1, 2024 21:08
@github-actions github-actions bot locked and limited conversation to collaborators Oct 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants