Skip to content

Make changes to the changelog#4342

Merged
sima-zhu merged 6 commits intoAzure:masterfrom
sima-zhu:storage_changelog
Jul 24, 2019
Merged

Make changes to the changelog#4342
sima-zhu merged 6 commits intoAzure:masterfrom
sima-zhu:storage_changelog

Conversation

@sima-zhu
Copy link
Contributor

@sima-zhu sima-zhu commented Jul 9, 2019

No description provided.

This BlobClient handles all blob types (block, page and append). Where operations can behave differently according to type (i.e. `upload`) the default behaviour will be block blobs unless otherwise specified.
- `StorageClient`: The StorageURL renamed to StorageClient. This client handles account-level operations. This includes managing service properties and listing the containers within an account.
- `ContainerClient`: The ContainerURL renamed to ContainerClient. The client handles operations for a particular container. This includes creating or deleting that container, as well as listing the blobs within that container.
- `BlobClient`: The BlobURL renamed to BlobClient. The client handles operations for a particular blob. This includes upload and download data.
Copy link
Member

Choose a reason for hiding this comment

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

Except we can't upload data with this client. I would have the last sentence be This includes downloading data and working with blob properties.

Copy link
Member

Choose a reason for hiding this comment

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

I'd also change a particular blob to an individual blob. I read "particular blob" and I think you're talking about the difference between block/page/append blobs, even more confusing when we talk about those on the very next line.

handles operations -> handles most operations, excluding upload,

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

- `StorageClient`: The StorageURL renamed to StorageClient. This client handles account-level operations. This includes managing service properties and listing the containers within an account.
- `ContainerClient`: The ContainerURL renamed to ContainerClient. The client handles operations for a particular container. This includes creating or deleting that container, as well as listing the blobs within that container.
- `BlobClient`: The BlobURL renamed to BlobClient. The client handles operations for a particular blob. This includes upload and download data.
There are subclients (BlockBlobClient, PageBlobClient, AppendBlobClient) available through all blob types (block, page and append), where operations can behave differently according to type (i.e. `upload`).
Copy link
Member

Choose a reason for hiding this comment

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

available through all blob types (block, page, and append), -> available for their respective blob types on the service

Also, it feels weird to say operations behave differently. They are either there or they are not. The only functionality that would behave differently with the same terminology would be blob input/output streams and uploadfromfile, but those aren't on the base class, so there's no method who's functionality is really changing.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for your comments. I will address these.

@sima-zhu sima-zhu requested a review from jaschrep-msft July 10, 2019 16:32
@sima-zhu sima-zhu requested a review from alzimmermsft July 23, 2019 20:45
This BlobClient handles all blob types (block, page and append). Where operations can behave differently according to type (i.e. `upload`) the default behaviour will be block blobs unless otherwise specified.
- `StorageClient`: StorageURL's functionality was migrated to StorageClient. This client handles account-level operations. This includes managing service properties and listing the containers within an account.
- `ContainerClient`: ContainerURL's functionality was migrated to ContainerClient. The client handles operations for a particular container. This includes creating or deleting that container, as well as listing the blobs within that container.
- `BlobClient`: StorageURL's functionality was migrated to StorageClient. The client handles most operations, excluding upload, for an individual blob, including downloading data and working with blob properties.
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't it be "BlobURL's functionality was migrated to BlobClient?

Can you also mention that TransferManager downloads were moved to BlobClient and TransferManager uploads were moved to BlockBlobClient?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed the comments.

Copy link
Member

Choose a reason for hiding this comment

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

Line 12 should say BlobClient not StorageClient.

@sima-zhu sima-zhu requested a review from rickle-msft July 23, 2019 21:13
Copy link
Member

@alzimmermsft alzimmermsft left a comment

Choose a reason for hiding this comment

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

LGTM, just replace the StorageClient name where BlobClient was expected.

@sima-zhu sima-zhu merged commit 916f511 into Azure:master Jul 24, 2019
@sima-zhu
Copy link
Contributor Author

The PR corrects some basic thing for changelog.
@alzimmermsft will continue work on changeLog for any improvement.

@sima-zhu sima-zhu deleted the storage_changelog branch July 24, 2019 17:41
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.

4 participants