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
The internal struct implementing the LargeObjectFile interface keeps track of which segments it has uploaded since {Dynamic,Static}LargeObjectCreate. When the upload fails (either during PUT of another segment or PUT of the manifest), it is useful to know which segments were already uploaded in order to perform cleanup.
Since LargeObjectFile does not have a method to expose its segments, one can only perform this cleanup by listing the uploaded segments, i.e.
However, this is prone to eventual consistency issues: The segments might not yet be visible in the container listing. I see two possible options:
Add a method like SegmentNames() []string to the LargeObjectFile interface.
Add a method Cleanup() error or Reset() error to the LargeObjectFile interface that deletes all segments which were uploaded since {Dynamic,Static}LargeObjectCreate.
The text was updated successfully, but these errors were encountered:
The internal struct implementing the
LargeObjectFile
interface keeps track of which segments it has uploaded since{Dynamic,Static}LargeObjectCreate
. When the upload fails (either during PUT of another segment or PUT of the manifest), it is useful to know which segments were already uploaded in order to perform cleanup.Since LargeObjectFile does not have a method to expose its segments, one can only perform this cleanup by listing the uploaded segments, i.e.
However, this is prone to eventual consistency issues: The segments might not yet be visible in the container listing. I see two possible options:
SegmentNames() []string
to theLargeObjectFile
interface.Cleanup() error
orReset() error
to theLargeObjectFile
interface that deletes all segments which were uploaded since{Dynamic,Static}LargeObjectCreate
.The text was updated successfully, but these errors were encountered: