Skip to content

Conversation

@MichaHoffmann
Copy link
Contributor

  • I added CHANGELOG entry for this change.
  • Change is not relevant to the end user.

Changes

Verification

Copy link
Member

@GiedriusS GiedriusS left a comment

Choose a reason for hiding this comment

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

Should we name it SizeBytes to avoid any kind of confusion over what are the units?

@MichaHoffmann MichaHoffmann force-pushed the mhoffmann/add-size-to-iter-with-attributes branch from 9bcf9fb to 3eea046 Compare September 3, 2025 06:43
@MichaHoffmann
Copy link
Contributor Author

Should we name it SizeBytes to avoid any kind of confusion over what are the units?

Yeah we can do that! Ill also implement it for the other providers a bit later!

for _, blob := range resp.Segment.BlobItems {
attrs := objstore.IterObjectAttributes{
Name: *blob.Name,
Size: *blob.Properties.ContentLength,
Copy link
Member

Choose a reason for hiding this comment

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

SizeBytes would be preferable, I think!


type IterObjectAttributes struct {
Name string
Size int64
Copy link
Member

Choose a reason for hiding this comment

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

Can the size be negative? Maybe let's use uint64.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Maybe as a canary for "this provider does not expose a size in iter"; idk if there is such a provider though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants