You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Too many writes on entities when committing chunks since we need to commit the upload and at the same time modify the record.
Describe the solution you'd like
At the end of uploading chunks, our gRPC client is using two messages: CommitChunk and UpdateRecord. The first function modify both the blob and record entities, and the second, the record entities. We suspect that this generates too many writes on entities. We would like a function that combines these operations.
Describe alternatives you've considered
Alternatives: perform the second calls asynchronously with a delay in a goroutine or by managing a queue of updates to perform. But I do not like the idea of introducing potential data inconsistency in our solution.
Additional context
The text was updated successfully, but these errors were encountered:
* feat: add CommitChunkedUploadWithUpdateRecord method
* update comments
* fix: validate record signature before updateing timestamp
* chore: add record as optional field to CommitChunkedUpload (#401)
* chore: address PR review related to unit tests
Co-authored-by: Frederic Loranger <[email protected]>
Is your feature request related to a problem? Please describe.
Too many writes on entities when committing chunks since we need to commit the upload and at the same time modify the record.
Describe the solution you'd like
At the end of uploading chunks, our gRPC client is using two messages: CommitChunk and UpdateRecord. The first function modify both the blob and record entities, and the second, the record entities. We suspect that this generates too many writes on entities. We would like a function that combines these operations.
Describe alternatives you've considered
Alternatives: perform the second calls asynchronously with a delay in a goroutine or by managing a queue of updates to perform. But I do not like the idea of introducing potential data inconsistency in our solution.
Additional context
The text was updated successfully, but these errors were encountered: